agentleFS
renanflustosarenanflustosa/octo-cluster/.claude/skills/pr-review/SKILL.md

pr-review

Skill3 starsChanged 23 days agoMITView on GitHub

Review a GitHub Pull Request for bugs, security, performance, and code quality. Use when user asks to review a PR or wants pull request feedback. Don't use for reviewing local uncommitted changes, creating new PRs, or merging branches.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use clack-cli-patterns, drag-to-reorder 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.
  • openchamberSkill

    clack-cli-patterns

    Use when creating or modifying OpenChamber CLI commands, prompts, terminal output, non-TTY behavior, `--quiet`, or `--json` behavior.

    Also in 3 projects that use this

  • openchamberSkill

    drag-to-reorder

    Use when implementing or modifying OpenChamber sortable or drag-to-reorder behavior, especially `@dnd-kit`, touch/mobile interactions, variable-width items, or wrapping layouts.

    Also in 3 projects that use this

  • jtenniswoodSkill

    expert-reset

    Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.

    Also in 3 projects that use this

  • CES-LtdSkill

    oss-pr

    Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

    Also in 3 projects that use this

  • CES-LtdSkill

    pr-automation

    PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

    Also in 3 projects that use this

  • +7 more from openchamber

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 180 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask mode. Arguments: $ARGUMENTS

    line 9
  2. Distinctive:

    If a focus mode is given, adjust the review:

    line 11
  3. Very specific:

    Run gh pr view [PR] and gh pr diff [PR] before reading files — the diff is the source of truth

    line 18
  4. Distinctive:

    Read surrounding files only when a finding needs context

    line 19
  5. Distinctive:

    Critical: - must fix before merge (bugs, security vulnerabilities)

    line 26
  6. Very specific:

    Use file:line references for all findings.

    line 30
  7. Very specific:

    If gh pr view fails → run gh auth status to verify authentication.

    line 42
  8. Distinctive:

    If a changed file is deleted in the PR → skip reading it.

    line 43
  9. Distinctive:

    If diff is too large → prioritize changed files with highest risk (auth, payments, data mutation)

    line 44

“Common” is measured: kept by at least 6 in 10 of the 180 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

Review Pull Request

Ask mode. Arguments: $ARGUMENTS

If a focus mode is given, adjust the review:

  • BUGS: Focus only on logical or other bugs
  • SECURITY: Focus only on security issues
  • PERFORMANCE: Focus only on performance issues

Workflow

  1. Run gh pr view [PR] and gh pr diff [PR] before reading files — the diff is the source of truth
  2. Read surrounding files only when a finding needs context
  3. Review based on mode (or all categories if no mode set)
  4. Provide structured feedback

Output format

Group by severity:

  • Critical - must fix before merge (bugs, security vulnerabilities)
  • Suggestions - improvements worth considering
  • Positives - good patterns to call out

Use file:line references for all findings. Include suggested fix for each critical issue.

See examples.md for output format and review-checklist.md for full checklist.

Rules

  • Review ALL changed files, not just the latest commit
  • Be specific: file:line + issue + suggested fix
  • Separate critical issues from suggestions

Error Handling

  • If gh pr view fails → run gh auth status to verify authentication; ask user for PR number if not on a PR branch
  • If a changed file is deleted in the PR → skip reading it; note it was removed
  • If diff is too large → prioritize changed files with highest risk (auth, payments, data mutation)

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.