Trim Reasoning Leakage

This skill is guidance, not a script. Reasoning leakage is prose whose vantage is the authoring session rather than the repository: it cites artifacts only that session could see, narrates a change instead of the state, or argues with a reviewer who has left.

When not to use

• Ordinary wording or contract problems. Use prose-standard instead.
• Decision records, postmortems, and alternatives-considered sections, which legitimately preserve history and rejected alternatives.
• Frozen records, generated catalogs, snapshots, and fixtures. Fix the owner, then regenerate.
• Deleting a fact because it sounds historical. Resolvability and durability are the tests, not tone.

Inputs and authorization

• Required: an explicit scope (paths, surfaces, or a diff). If missing, report it and stop; do not assume repository-wide.
• Authorization: an audit is read-only. Edit only when the task asks for a fix. Fixing a citation never authorizes changing the behavior it describes.

Method

The one test