agentleFS
Sign inStart free
raomasterraomaster/skills/pr-review/SKILL.md

pr-review

Skill1 starsChanged 7 months agoMITView on GitHub

Use when reviewing PRs, reading code review feedback, or responding to review comments from Codex, bots, or teammates. Triggers on "review PR", "check PR comments", "what did Codex say", "PR feedback".

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use oss-pr, pr-automation 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.
  • 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

  • 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

  • jtenniswoodSkill

    updates

    Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.

    Also in 3 projects that use this

  • 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

  • +6 more from openchamber

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When reviewing a PR, use gh api to fetch inline review comments — they are NOT visible with gh pr view --comments.

    line 8
  2. Distinctive:

    If valid, fix it. If not, explain why.

    line 35
  3. Very specific:

    Use --jq to format results readably:

    line 39

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

PR Review Comments

When reviewing a PR, use gh api to fetch inline review comments — they are NOT visible with gh pr view --comments.

How to fetch PR review comments

# For a specific PR number:
gh api repos/{owner}/{repo}/pulls/{pr_number}/comments --jq '.[] | {path: .path, line: .line, body: .body, user: .user.login}'

# Or for the current branch's PR:
PR_NUMBER=$(gh pr view --json number --jq '.number')
gh api repos/{owner}/{repo}/pulls/$PR_NUMBER/comments --jq '.[] | {path: .path, line: .line, body: .body, user: .user.login}'

Key insight

gh pr view --comments only shows issue-level comments. Inline code review comments live in a different API endpoint:

  • Issue comments: gh pr view --comments or gh api .../issues/{n}/comments
  • Review comments (inline): gh api .../pulls/{n}/comments
  • Reviews (summary): gh api .../pulls/{n}/reviews

Workflow

  1. Get the PR number: gh pr view --json number --jq '.number'
  2. Fetch inline comments: gh api repos/{owner}/{repo}/pulls/{pr_number}/comments
  3. For each comment, read the file at the referenced line
  4. Evaluate whether the comment is valid
  5. If valid, fix it. If not, explain why.

Formatting the output

Use --jq to format results readably:

gh api repos/{owner}/{repo}/pulls/$PR/comments --jq '.[] | "\(.path):\(.line) — @\(.user.login)\n\(.body)\n"'

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.

Check your setup, free