chisle-audit

1# Chisle Audit
2 
3Scan the target (a diff, a file, or the repo tree) and report what to cut, on
4both axes. One-shot. Read-only: never edit, never write a flag, never apply fixes.
5 
6## Scope
7 
8- No argument → audit the current `git diff` (staged + unstaged). Empty diff → audit `HEAD~1..HEAD`.
9- A path → audit that file or directory.
10- "repo" / "whole repo" → walk the tree (skip vendored/generated/`node_modules`/`dist`/lockfiles).
11 
12## What to flag
13 
14**Code (the YAGNI axis):**
15- Reinvented stdlib (hand-rolled debounce, deep-clone, groupBy, retry loop, date math)
16- Abstraction with one implementation (interface/factory/wrapper for a single case)
17- New dependency for what a few lines or an installed dep already covers
18- Config/option/flag that never varies
19- Speculative "for later" scaffolding with no current caller
20- Verbose code where a native platform feature (CSS, DB constraint, `<input type>`) does it
21 
22**Prose (the compression axis), the half a code-only auditor misses:**
23- Comments that restate the code (`i += 1  // increment i`)
24- Docstrings/READMEs padded with filler, hedging, ceremony, or duplicated content
25- Multi-paragraph explanations where one tight sentence carries the meaning
26- Decorative tables/emoji/headings that add tokens, not information
27- Dead prose: TODO graveyards, stale "see also" links, obsolete sections
28 
29## What NOT to flag
30 
31Input validation at trust boundaries, error handling that prevents data loss,
32…