← ClaudeAtlas

staff-level-reviewlisted

Read-only engineering review with a fixed findings/verdict output contract. Use when the review needs that contract, a review context bundle, or a non-GitHub diff source (e.g. Azure DevOps, a patch file, a bounded set of repos and docs). For routine review of a local diff or GitHub PR, prefer the built-in /code-review or /review instead.
justinmchoi/ai-toolkit · ★ 1 · Code & Development · score 74
Install: claude install-skill justinmchoi/ai-toolkit
# Staff-Level Review Use this as a read-only engineering review checkpoint. Produce findings and a verdict; do not edit files, push changes, or post PR comments unless the user explicitly switches to a separate review-fix or posting workflow. If `docs/specs/0004-staff-level-review.md` exists in the current repo, it is the fuller definition and takes precedence. If it does not exist, this file is self-contained — do not go looking for the spec elsewhere. ## Inputs Review any bounded diff source: - PR number, URL, branch, or local diff - provided patch or diff file - review context bundle - changed files plus related docs, ADRs, CONTEXT files, and CI/test signals If the diff source is ambiguous, ask before reviewing. ## Preflight Before reviewing, decide whether to proceed: ```text proceed: yes | no | needs-info reason: required_context: suggested_next_action: ``` Stop instead of forcing a low-confidence review when the PR is closed/merged, the diff is too large, requirements are missing, context is insufficient, or extra repositories are needed but not approved. ## Review Scope Review for high-signal issues across: - correctness and regressions - architecture and responsibility boundaries - security and privacy - performance and unbounded work - test quality and missing behavior coverage - maintainability and naming - API/interface design - breaking changes and migration risk - operability, rollout, observability, and rollback - requirement compliance Apply a fal