agentleFS
Sign inStart free
ShahriarBijoyShahriarBijoy/show-me-how/skills/pr-review/SKILL.md

pr-review

Skill0 starsChanged 3 months agoMITView on GitHub

Draw the picture of what a PR does — before/after and request-path illustrations plus a brief summary, saved as docs/show-me-how/pr-<n>-<slug>/pr-<n>-<slug>.md. Not a bug/style review; see /code-review for that.

  • Commits and pushes

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
  • Other versions195 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 195

    1. Significant-Gravitas/AutoGPT★ 188ksame name
    2. pytorch/pytorch★ 105ksame name
    3. rtk-ai/rtk★ 86ksame name
    4. saadeghi/daisyui★ 43ksame name
    5. rustfs/rustfs★ 36ksame name
    6. dotnet/maui★ 23ksame name
    7. NVIDIA/Megatron-LM★ 18ksame name
    8. MiniMax-AI/skills★ 14ksame name
    9. btriapitsyn/openchamber★ 13ksame name
    10. openchamber/openchamber★ 13ksame name

    185 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 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.

  • 4

    Very specific

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

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

    Never run gh pr comment, git commit, or git push.

    line 11
  2. Very specific:

    If $ARGUMENTS is empty, run gh pr view --json number (resolves the PR for the current branch).

    line 15
  3. Very specific:

    If gh is not installed or not authenticated, tell the user exactly: "Run gh auth login, then try again." Stop.

    line 17
  4. Very specific:

    If the command errors or returns no PR, stop with one line: "No PR found for $ARGUMENTS." (or "for the current branch" if empty).

    line 18
  5. Distinctive:

    Write BRIEF (<=200 words): what changed, why (from the body/commits), how the pieces connect, what a reviewer should look at first, the one …

    line 28

“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

/show-me-how:pr-review $ARGUMENTS

This is "the picture of what this PR does" — the thing a reviewer looks at before reading the diff. It is not a bug or style review; use /code-review for that.

Never run gh pr comment, git commit, or git push. This command only reads with gh and writes files under the docs folder.

1. Resolve the PR number

  1. If $ARGUMENTS is empty, run gh pr view --json number (resolves the PR for the current branch).
  2. Otherwise $ARGUMENTS is a PR number or a full GitHub PR URL — run gh pr view $ARGUMENTS --json number (gh accepts either form).
  3. If gh is not installed or not authenticated, tell the user exactly: "Run gh auth login, then try again." Stop.
  4. If the command errors or returns no PR, stop with one line: "No PR found for $ARGUMENTS." (or "for the current branch" if empty).
  5. N = the resolved number. URL = the PR's url (read it in step 2 along with the rest).

2. Gather (read-only)

  1. gh pr view N --json title,body,baseRefName,headRefName,files,additions,deletions,commits,url
  2. gh pr diff N — if it is more than ~1500 lines, do not read it all: read only the file list from step 1 and the first 300 lines of the diff, and note in the brief that the summary is partial.

3. Brief

Write BRIEF (<=200 words): what changed, why (from the body/commits), how the pieces connect, what a reviewer should look at first, the one risk.

4. Illustrate

MAX_IMAGES = 4. Beats: before → what changed → after, plus one twist panel if the PR carries a risk; a tiny PR (<=2 files) may be a single before/after panel.

Invoke the illustrate skill (skills/illustrate/SKILL.md) from its step 0, with this brief block:

MODE: doc
TOPIC: pr-N-<title>
SOURCES: <files changed from step 2.1>, <URL>
BRIEF: <the text from step 3>
MAX_IMAGES: 4

5. Report

Illustrate writes docs/show-me-how/pr-N-<slug>/pr-N-<slug>.md. After it finishes, print:

  1. A 5-line "what this PR does" summary.
  2. The image paths it produced.
  3. The doc path.
  4. This offer, without running it: "Post this as a PR comment? Run: gh pr comment N --body-file <doc>"

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