docs: extend concision rules to GitHub prose - #325
Merged
Conversation
The "Be concise" rule was scoped to responses and code comments, so PR descriptions and issue bodies kept accumulating restated summaries and checklists that duplicated prose already above them. Extend the rule to GitHub prose and name the specific failure modes, alongside the existing hard-wrap scope note. Key changes: - Add a GitHub PR / Issue / Comment Conventions section - Require saying things once, leading with the problem, and cutting words that carry no fact, while compressing rather than omitting
1 task
JoseSzycho
approved these changes
Jul 30, 2026
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
2 participants
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.
Summary
CLAUDE.mdsays "Be concise. Always", but scopes it to responses and code comments. PR descriptions and issue bodies fall outside it, and it shows: summaries restated verbatim as test-plan checkboxes, and several paragraphs re-selling the same point.This extends the rule to GitHub prose and names the failure modes, next to the hard-wrap scope note from #323.
The compress-don't-omit clause is deliberate — the goal is fewer words, not fewer facts.
Test plan