feat(claude): add reporting-order guidance to global CLAUDE.md - #778
Open
ppat wants to merge 2 commits into
Open
feat(claude): add reporting-order guidance to global CLAUDE.md#778ppat wants to merge 2 commits into
ppat wants to merge 2 commits into
Conversation
Findings were being relayed in discovery order (mechanism first, significance last), which reads as more urgent or more relevant than it is. Add a "Reporting findings" section requiring verdict first, explicit significance classification, and mechanism/detail last or on request.
A format asked for once (table, list, diff, brevity level) was being honored for a single reply, then dropped on the next update on the same topic. Extend the reporting-order section: a requested format holds for the rest of that thread of work until told otherwise.
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
1 participant
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
Adds a "Reporting findings" section to
private_dot_claude/CLAUDE.md(renders to~/.claude/CLAUDE.md).The defect this fixes: findings were being reported in the order they were discovered rather than the order the reader needs them — mechanism and detail up front, with the verdict (does this matter, does it need action) arriving last or only after being asked for directly. The information was accurate but the ordering made it read as more significant or more urgent than it was, and cost the reader's attention establishing that.
The rule: lead with the verdict, classify significance explicitly (active problem / latent-and-not-currently-triggered / background), say plainly when something isn't a problem and why it's being mentioned at all, then downstream implications, then a recommendation (including "do nothing" as a legitimate one), with mechanism/evidence last or on request. Also covers a related, second failure mode: a requested output format (table, list, diff, brevity level) being honored for one reply and then dropped on the next update on the same topic — the rule makes a requested format persist for that thread of work until told otherwise. Both are written generically — they apply to research results, incident write-ups, code review, subagent summaries, or answering a direct question, not any one domain.
Placement
Added as a new
##section after "How to work", since none of the existing sections (Interpreting requests / When to ask vs. proceed / How to work) cover output structure — this fills a gap rather than competing with or overriding anything already there.Test plan
markdownlint-cli2 --config .markdownlint-cli2.yaml private_dot_claude/CLAUDE.md— 0 issuespre-commit run --files private_dot_claude/CLAUDE.md— all hooks passlint.yaml):markdown/markdownlint,detect-changes,pre-commitpass;chezmoi,shellcheck,yaml,zizmor,github-actions,renovate-config-checkskipped (path filters — markdown-only change)