fix: documentation skills should preserve detail readers need #130
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/doc-fact-authority"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gives documentation authors one standard for fact ownership and reader needs. Necessary contracts, warnings, and derived values stay where readers act; unnecessary maintenance copies still require removal. These instructions are already included in the deployed reviewer hotfix.
The suite passes 172 of 173 tests; the keeper-path assertion in
audit-checkouts.test.mjs:2248also fails onmain.Merge before the runner pin update. Its
check:skill-pinrequires both complete skill directories at the pinned revision to match the default branch. Squash or rebase merges work if those directories remain identical.Review
01M4E85RQ2W046Y9J9H3BACAAX— headc40df477f3d6989e0fddb2e393164c94d400b347Review — j4k-oss/agent-skills @
f3c2243da4Scope: diff against base tree
8e004ccf90c2Status: dispatched — coverage complete (4/4 slots terminal)
Facts: current review-wide projection
Computed under:
Findings (0)
No findings survived.
Reviewed:
Other claims
01M4E87N1RP6KVRTT7DP70H52Flow — project-docs states the one-authority/task-serving-copy rule three times in the same file01M4E87WCXJFG2TP9WDRD0RF7Zlow — writing-for-agents' new 'One Idea, One Place' paragraphs repeat each other and add reviewer-facing no-op sentencesCoverage
Coverage pass: 01M4E8681JVPDWRZSJXXZJMQR4
Accounting: complete
Slot health: healthy
Investigated both unadjudicated low-severity claims against the full changed skills at
c40df477f3d6989e0fddb2e393164c94d400b347:01M4E87N1RP6KVRTT7DP70H52F: the three project-docs passages govern different operations. Division of labor chooses a fact's authority and permits task-serving presentations; maintenance routes stray-document duplicates into the scoped consolidation workflow; consolidation requires moving before removal, preserves necessary local meaning, deletes empty files, and prohibits information loss. Removing those later instructions merely because they apply the same principle would remove distinct operational constraints. The shared principle is consistent across them; repeated subject matter alone does not establish a redundant instruction.01M4E87WCXJFG2TP9WDRD0RF7Z: the new writing paragraphs distinguish derived displays, task-required exact details, when a source lookup is sufficient, and when a manual copy should be removed. These answer different decisions, including the diagnostic/interface and source-access boundaries needed to prevent the observed contradictory reviews. This skill explicitly serves both writing and reviewing agent instructions, so those review-facing boundaries are within its stated audience. No sentence identified by the report can be removed on the title's evidence without first showing that its boundary is preserved elsewhere.Neither claim demonstrates a defect in this revision. Retaining these distinct constraints preserves the accepted behavior; this is not a general exemption from removing redundant instructions.