nitpickerlisted

# Nitpicker Adversarial, exhaustive code review and auditing. Assumes the code is incorrect until proven otherwise. One skill, many commands. ## Dispatch The text following the invocation is parsed as: ```text /nitpicker [command] [extra instructions] ``` - The **first word** names the command. Match it against the tables below — canonical names and aliases both resolve. Unknown first word or no text at all → run the default `audit` command and treat all text as extra instructions. - **Everything after the command** is extra instructions constraining that run (scope, focus, thresholds). The modifiers `inline` and `changed-files` may appear anywhere in it (see `commands/_conventions.md`). - Agents without argument substitution (Copilot, pi) pass the same text after the skill invocation; parse it identically. Execution order, always: 1. Read [commands/_conventions.md](commands/_conventions.md) — it binds every command (severity levels, findings store protocol, rules). 2. Read `commands/<command>.md` for the resolved command. 3. Execute it with the extra instructions applied. Never chain commands on your own; run exactly the one resolved command (commands may themselves direct you to run another first — follow that). ## Commands Grouped by category. Aliases in the purpose text (mostly the 1.x skill names) remain legitimate invocations; the dispatcher resolves them to the same command file (e.g. `test-auditor` → `commands/tests.md`, `loopholes` → `command