← ClaudeAtlas

inspectlisted

Two-verdict code review (spec compliance + quality); findings need evidence, severity rationale, confidence. Triggers: 'inspect', 'review this change'.
dyasnurhakim/smithy-claude · ★ 0 · Testing & QA · score 67
Install: claude install-skill dyasnurhakim/smithy-claude
# Inspect — Two-Verdict Review Read `${CLAUDE_PLUGIN_ROOT}/references/creed.md` and `${CLAUDE_PLUGIN_ROOT}/references/dispatch.md` first. Log: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/ledger.sh append inspect <slug> <unit> STARTED -` ## Determine scope - **Pipeline mode** (called from forge): brief + base sha already exist — the review package was built by forge; skip to Dispatch. - **Standalone mode**: ask the user what to review and against what base (default: merge-base with the default branch). Write an ad-hoc brief at `$SMITHY_MEM/jobs/adhoc-<date>/briefs/review-brief.md` capturing what the change is SUPPOSED to do (from the user's description — ask, don't infer silently). Then: `review-package.sh record-base` is NOT appropriate here (HEAD is the work); instead set the base explicitly in STATE.md or pass a package built with `git diff <base>..HEAD` semantics via `bash ${CLAUDE_PLUGIN_ROOT}/scripts/review-package.sh build <brief> <out>` after writing the base sha into STATE.md's `- Base sha:` line. ## Dispatch 1. Resolve routing: `bash ${CLAUDE_PLUGIN_ROOT}/scripts/routing.sh review` 2. Dispatch the `smithy:inspector` agent (model from routing). Prompt = effort banner + paths only: review package, creed, report output path (`jobs/<slug>/reports/<unit>-review.md`) + this line verbatim: **"Do Not Trust the Report — the forger's claims are unverified. Verify each one against the diff and by running read-only checks."** ## Present results 3.