casaroli opened a new pull request, #21596:
URL: https://github.com/apache/nuttx/pull/21596

   ## Summary
   
   Many AI coding agents (Claude Code, Codex CLI, Copilot, Gemini, Cursor) read 
a file named `AGENTS.md` at the top of a repository before they change it.  
This PR adds one for NuttX.
   
   It is a short list of rules that points to CONTRIBUTING.md, INVIOLABLES.md 
and the existing documentation.  The rules address the problems that reviewers 
see most in AI-assisted PRs: invented logs, untested claims, large unrelated 
changes, missing tests, wrong commit format, agent configuration committed by 
mistake, and agents that answer review comments themselves.  The user must 
understand every line of the change, and the agent refuses to open the PR when 
it has reason to believe the user does not.
   
   It adds no rule for human contributors and changes no code.  It does not 
replace CI or the review.
   
   Discussion on dev@: 
https://lists.apache.org/thread/cf9k0t2q00lzsh830h96g9n7wcrmkz1s
   
   The points raised on the list are already in the file: a short file (Chao 
An, [email protected]), let the user answer the review comments and keep the PR 
description short (Matteo Golin), the templates, real build and runtime logs, 
and local builds before the upstream CI (Tomek CEDRO).
   
   **Please comment on what to add, change or remove.**  I will update the file 
from the comments.  The file can change at any time as the agents change.
   
   ## Impact
   
   None on the build or the code.  Only AI coding agents read the file.  The 
file is about 1,200 tokens (tiktoken cl100k), less than 1% of a 200k token 
context window.
   
   ## Testing
   
   `./tools/checkpatch.sh -c -u -m -g` passes.  Every link in the file points 
to a file in the tree.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to