agentleFS
fpindejfpindej/netrock/.claude/skills/review-pr/SKILL.md

review-pr

Skill234 starsChanged 3 months agoMITView on GitHub

Reviews a pull request for production-readiness. Use when reviewing PRs, checking code changes before merge, or when asked to evaluate a PR.

185 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use diagnose-ci-failures, docs-loop and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zerx-labSkill

    diagnose-ci-failures

    Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

    Also in 3 projects that use this

  • GeiserXSkill

    docs-loop

    Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.

    Also in 3 projects that use this

  • GeiserXSkill

    full-loop

    Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.

    Also in 3 projects that use this

  • n24q02mSkill

    review-delta

    Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

    Also in 3 projects that use this

  • n24q02mSkill

    build-graph

    Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.

    Also in 3 projects that use this

  • +7 more from GeiserX

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read actual source files when a finding needs context - not just the diff

    line 48

“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reviews a pull request for production-readiness before merge. Runs in the main session so the reviewer agents can be dispatched in parallel (per CLAUDE.md delegation patterns).

Argument: PR number or URL. If omitted, reviews the current branch's open PR.

Current branch: !git branch --show-current Open PR for this branch: !gh pr view --json number,title,url --jq '"#\(.number) \(.title) - \(.url)"' 2>/dev/null || echo "(no open PR)"

Steps

  1. Resolve the PR: gh pr view {number} --json number,title,headRefName,body
  2. Get the diff and changed files: gh pr diff {number}, gh pr view {number} --json files
  3. Dispatch reviewer agents in parallel (one message, multiple Agent calls), scoped by what changed:
    • backend-reviewer - if src/backend/ changed
    • frontend-reviewer - if src/frontend/ changed
    • security-reviewer - always
    • ux-designer - if UI components or pages changed Give each the PR number and the changed-file list for its scope. They preload the convention skills - do not restate conventions in the prompt.
  4. While reviewers run, perform the cross-cutting checks below yourself.

Orchestrator Checks (cross-cutting)

  • Intent: does the code do what the PR description says?
  • Cross-stack consistency: backend DTO changes -> types regenerated (v1.d.ts), frontend consumers updated
  • i18n: new keys present in ALL locale directories
  • Dockerfile: new .csproj referenced by WebApi has a COPY line in the restore layer
  • Completeness: new flags/props consumed; no dead code introduced
  • No em dashes (U+2014), no emojis anywhere in the diff
  • Tests: behavior changes come with test changes

Verdict Synthesis

Merge the reviewer reports and your own checks into one report:

  • PASS - what looks good (brief, no padding)
  • FAIL - issues that MUST be fixed before merge (with file path and line, attributed to the reviewer that found them)
  • WARN - suggestions, not blockers

Final verdict: REQUEST CHANGES if any reviewer reported FAIL/CRITICAL/HIGH items or your checks found blockers; APPROVE WITH SUGGESTIONS if only WARN items; otherwise APPROVE.

Rules

  • Research only - do NOT modify any files
  • Read actual source files when a finding needs context - not just the diff
  • Be thorough but not pedantic - flag real issues, not style nitpicks already handled by linters
  • For a quick generic pass without project reviewers, the built-in /code-review is also available; this skill is the convention-aware review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.