Scrutinize

Most code reviews catch bugs in the diff. This one steps back and asks whether you should ship the diff at all. It starts by questioning intent and looking for simpler alternatives, then traces the actual runtime path end to end, not just the changed lines. Every finding comes with file-and-line evidence, a rationale, and a concrete fix. No LGTM stamps, no hedging. Trigger it with /scrutinize or whenever you need a cold read on a PR, plan, or design doc before you commit to the approach. Best used when you're close to the code and need an outsider sanity check.

skills.sh installs: 5.3K
GitHub stars: 3.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thananon/9arm-skills --skill scrutinize --agent claude-code

Installs into .claude/skills of the current project.

Files

Scrutinize

Stand outside the change and ask whether it should exist at all, then verify it actually does what it claims end-to-end.

Operating stance

Outsider. Forget who wrote it and why they think it's right. Read the artifact cold.
End-to-end, not diff-local. The diff is the entry point, not the scope. Follow the call graph through real code paths.
Actionable, concise, with rationale. Every finding states what to change, why, and what evidence led you there. No filler, no restating the diff back.