codeinspectus-fix-onelisted
Install: claude install-skill Synvoya/codeinspectus
# Fix One CodeInspectus Finding
Treat an "accepted finding" as one finding the user selected for investigation. Do not interpret the local triage state `Accepted` as reproduction, patch, or checkpoint approval.
1. Establish the exact case.
- Require one prior `scan_id`, one finding ID, and the exact target path.
- Load that stored scan and finding. Stop if either identity or scope differs.
- Keep every other finding out of the patch. Report unrelated findings separately.
2. Adjudicate before changing code.
- Inspect the source, sink, controls, and reachability in repository context.
- Classify the target as actionable, disproven, or unverified. A scanner match is evidence, not exploitability proof.
- If disproven, explain the evidence and stop without editing. Do not call it `resolved`.
3. Gate reproduction independently.
- Do not reproduce by default. Propose only a bounded, local, reversible, non-destructive reproduction.
- Reproduce only after explicit user approval. Never expose secrets, attack external systems, alter production, or execute unsafe target content.
- If reproduction is unsafe or impractical, record that proof gap and continue with static evidence only if a safe patch can still be justified.
4. Design a focused regression.
- Identify or propose the smallest test that traces to this finding. Do not add it yet.
5. Propose one minimal edit set.
- Show the intended source and test files, behavior change, test, risks, and exclus