Agents: trim boilerplate that agents already follow#308
Merged
Conversation
humitos
approved these changes
Jun 2, 2026
Base automatically changed from
claude/agents-pr-description-guidelines-OMdXH
to
main
June 2, 2026 15:08
Member
Author
|
@copilot resolve the merge conflicts in this pull request |
Copilot
AI
force-pushed
the
claude/agents-trim-boilerplate
branch
from
June 2, 2026 15:12
96306c9 to
6e831c1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HS: I asked the agent how to improve the Agent file, and this is what it came up with. And they can make sense, we should only be stating things that are unique to our codebase. It knows to follow the existing style.
AGENTS.mdtells agents to cut filler, then spends whole sections on advice any competent agent already follows — PEP 8, "be aware of OWASP", "write descriptive test names." That boilerplate buries the rules that are genuinely RTD-specific and easy to get wrong (thetoxrecipes, the migration check, the marketing-names rule). Removing it so the guidance that remains is worth reading.If any of the dropped sections was load-bearing for a reason I'm missing, say so and I'll restore it — ideally replaced with a concrete, RTD-specific rule rather than a placeholder.
Stacked on #307 to avoid conflicts on the same file; rebase onto
mainonce that lands.