← ClaudeAtlas

nitpickerlisted

Hostile audit toolkit: one entry point dispatching specialist commands — adversarial review, security, tests, docs, types, architecture, performance, reliability, caching, concurrency, error handling, resource leaks, dependencies, licensing, CI, commits, migrations, observability, API contracts, a11y, i18n, privacy, config, infrastructure-as-code, prompt safety, installed agent configuration, complexity, dead and unwired code, agent rule and hook enforcement, plus planning, plan execution, teaching, triage, PR review and review-comment implementation. Use when auditing or reviewing a repository, PR, or any quality dimension of a codebase — "audit this", "review the whole codebase", "find all problems", "exhaustive review", "/nitpicker <command>", a release gate check, or any specific audit ask (security scan, find race conditions, audit the tests, hunt dead code, is this installed skill safe, plan a change, teach me this codebase, review the PR, fix the CR comments).
ivuorinen/skills · ★ 3 · AI & Automation · score 62
Install: claude install-skill ivuorinen/skills
# 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. Load [commands/_conventions.md](commands/_conventions.md) — it binds every command (severity levels, findings store protocol, rules). `np_read_reference` with `name: "conventions"` when the session exposes the nitpicker MCP tools, else read the file directly. 2. Load the resolved command: `np_read_command` with `command: <command>` when the session exposes the nitpicker MCP tools, else read `commands/<command>.md` directly. 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 th