scrutinize

Trace code paths end-to-end and report actionable review findings.

3.1k|415|Updated May 20, 2026
One-click install
npx skills add https://github.com/thananon/9arm-skills --skill scrutinize-thananon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrutinize
Source: https://github.com/thananon/9arm-skills/tree/main/skills/engineering/scrutinize
Command: npx skills add https://github.com/thananon/9arm-skills --skill scrutinize-thananon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Outsider-perspective end-to-end review of a plan, PR, or code change.

Core Features & Use Cases

  • Outsider-first questioning of intent and potential simpler alternatives.
  • Trace the actual code path end-to-end, not just the diff.
  • Produce concise, actionable findings with rationale and evidence.
  • Trigger on reviews, audits, or sanity checks for plans, PRs, diffs, design docs, or proposed code changes.

Quick Start

Ask me to scrutinize the proposed change end-to-end and return a concise, rationale-backed report.

Frequently Asked Questions about scrutinize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform an end-to-end code review from an outsider perspective?

An outsider end-to-end code review traces actual code paths from entry to exit, questions intent, evaluates simpler alternatives, and delivers a structured report with findings, rationale, and evidence rather than just focusing on diffs.

What is the best way to audit a proposed code change or design doc?

Auditing a proposed code change involves verifying claims with evidence, evaluating potential simpler alternatives, and producing concise, actionable findings with rationale to ensure the plan holds up under scrutiny.

How do I trace the real execution path of a PR instead of just checking the diff?

Tracing the real execution path of a PR requires following the actual code paths from entry to exit across the codebase, verifying claims with concrete evidence, and questioning the original intent rather than reviewing isolated diff changes.

Can I use this approach to sanity check a software engineering plan before implementation?

Yes, you can trigger an outsider-perspective sanity check on software engineering plans, proposed code changes, or design docs to question intent and evaluate simpler alternatives before implementation begins.

What should an actionable code audit report include?

An actionable code audit report should include structured findings, rationale backed by evidence, traced end-to-end code paths, and suggested improvements for the proposed changes.