What problem does it solve?
Prevents accidental regressions and hidden breakages by requiring context and evidence before removing or simplifying code that may have historical or environmental reasons for existing.
Core Features & Use Cases
- Context-first audit: A stepwise protocol to pause, investigate history, and verify intent before changing or deleting code.
- Archaeology & interrogation: Guidance to use git blame, commit inspection, and repository search to uncover reasons for odd or "ugly" code.
- Risk triage & decision matrix: Prioritizes investigation depth based on blast radius and recommends KEEP, REFACTOR, DELETE, or FLAG.
- Rubber-duck validation: Enforces explaining code in plain English as a safety check before making irreversible edits.
- Self-improvement logs: Optional learning artifacts to capture recurring patterns and corrections for future detection.
Quick Start
Use the chestertons-fence skill to audit a risky code change by performing git archaeology, explaining the logic in plain English, and documenting your decision before deleting anything.
