guarding-destructive-operations

Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of the first mutation, structural classification rather than string-prefix matching, name validation plus resolved-path containment as two independent checks, why a guard on the destructive path is invisible to the dry-run, and mutation-testing each half separately. Use when writing or reviewing a `--rebu

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-tool-design 456,474 ★
  Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and E
• code-review 323,337 ★
  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does th
• codebase-design 323,337 ★
  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interfac
• domain-modeling 323,337 ★
  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLO
• implement 323,337 ★
  Implement a piece of work based on a spec or set of tickets.