← ClaudeAtlas

review-prlisted

This skill should be used when the user asks to "review this PR", "audit this pull request", or assess a PR for code quality, security, and correctness.
lklimek/claudius · ★ 1 · Code & Development · score 74
Install: claude install-skill lklimek/claudius
# PR Audit Workflow Runs inline (not forked) so it — and the `/claudius:grumpy-review` it invokes in §3 — keeps the `Agent` tool for fan-out. `<plugin-root>` in [pr-review.md](../git-and-github/references/pr-review.md) commands is `${CLAUDE_PLUGIN_ROOT}` — write it exactly so the `allowed-tools` rules match. ## 1. Gather PR Context Load `/claudius:git-and-github`. Fetch PR metadata, changed files, and diff per [pr-review.md](../git-and-github/references/pr-review.md) § Get PR Context — files and diff via the subagent pattern in `git-and-github` § Context Management. Local git for commit history and detailed diffs. ### Context Digest **The single definition of "the digest"** — other skills point here, none redefines it. An ordered list of `{source, claim}` entries plus four narrative fields: ``` Promises: <ordered {source, claim} list per the intent priority in `claudius:severity` § Merge Classification> Goal: <one line — what this PR is for> Non-goals: <PR body Out-of-scope/Non-goals sections + session knowledge> Operational profile: <per touched area: invocation (user action / cron / admin one-time), concurrency reality, failure cost — each claim WITH its evidence: entry-point trace, doc link, or explicit human statement> Architecture rationale / UX-DX priorities: <relevant prior decisions — MemCan, session> ``` Source priority for every field: 1. Explicit user/session requirements, acceptance criteria, and statements the coordinator already holds 2. Linked issue