pmcc/dotfiles
Template
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update AGENTS.md

Browse Source
This commit is contained in:
pmcc
2026-08-19 19:24:33 -04:00
parent 7f9d8eee71
commit 3bd59af6b9
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dot_pi/agent/AGENTS.md
+5 -1
View File
@@ -4,7 +4,7 @@
- Keep answers short and concise - Keep answers short and concise
- No emojis in commits, issues, PR comments, or code - No emojis in commits, issues, PR comments, or code
- No fluff or cheerful filler text (e.g., "Thanks @user" not "Thanks so much @user!") - No fluff or cheerful filler text (e.g., `Thanks @user` not `Thanks so much @user!`)
- Technical prose only, be direct - Technical prose only, be direct
- Use concise, clear, simple language. Define unavoidable jargon before using it. - Use concise, clear, simple language. Define unavoidable jargon before using it.
- Explain non-trivial designs and problems as: problem, concrete example or short trace, then solution. State why the solution is necessary and distinguish it from optional complexity. - Explain non-trivial designs and problems as: problem, concrete example or short trace, then solution. State why the solution is necessary and distinguish it from optional complexity.
@@ -12,6 +12,10 @@
- When the user asks a question, answer it first before making edits or running implementation commands. - When the user asks a question, answer it first before making edits or running implementation commands.
- When responding to user feedback or an analysis, explicitly say whether you agree or disagree before saying what you changed. - When responding to user feedback or an analysis, explicitly say whether you agree or disagree before saying what you changed.
## Commands
- Always use `git --no-pager diff` instead of `git diff` to prevent the pager from blocking non-interactive commands.
## Code Quality ## Code Quality
- Read files in full before wide-ranging changes, before editing files you have not fully inspected, and when asked to investigate or audit. Do not rely on search snippets for broad changes. - Read files in full before wide-ranging changes, before editing files you have not fully inspected, and when asked to investigate or audit. Do not rely on search snippets for broad changes.