What problem does it solve?
Handover notes, prepared comments, verdict files, and previous session summaries contain claims that may no longer match the current codebase, and publishing them unverified puts stale or invented statements in the user's name.
Core Features & Use Cases
- Claim Re-derivation: Requires every inherited conclusion to be re-derived from primary sources such as code, APIs, configs, and actual command output before it reaches a tracker comment, PR description, or message.
- Reason Verification: Distinguishes correct verdicts from invented explanations, ensuring the stated reason for an action is checked, not just the action itself.
- Batch Review Guard: Treats piles of pre-written items as unverified claims rather than completed work, preventing bulk approval of stale content.
- Use Case: When resuming a task from a previous agent's summary claiming a feature was removed in a release, check the call site at the released tag with git show before repeating that claim in an issue comment.
Quick Start
Load this skill whenever a task starts from handover notes or a previous session's conclusions, then verify each inherited claim against the current code before publishing anything.