pr-review
Skill44 starsChanged 5 months agoApache-2.0View on GitHub
Workflow for reviewing pull requests via GitHub MCP or GitHub CLI (gh) and team coding standards. Use when reviewing PRs, checking code quality, or providing structured review feedback.
- Reads credentials
195 other projects use a version of this.
Adopted by
Most recently taken up by
- IntelRealSense/librealsensetheir own version, first seen Nov 16, 2026
- wikimedia/wikipedia-iostheir own version, first seen Nov 16, 2026
- realsenseai/librealsensetheir own version, first seen Nov 16, 2026
- minio/skillstheir own version, first seen Nov 16, 2026
- lumlaolao/spike-evaltheir own version, first seen Nov 16, 2026
- AshrafDurjoy/genai-shared-patternstheir own version, first seen Nov 16, 2026
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.
openchamberSkillclack-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
openchamberSkilldrag-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
jtenniswoodSkillexpert-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-LtdSkilloss-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-LtdSkillpr-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
Other versions195 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 195
- Significant-Gravitas/AutoGPT★ 188ksame name
- pytorch/pytorch★ 106ksame name
- rtk-ai/rtk★ 87ksame name
- saadeghi/daisyui★ 43ksame name
- rustfs/rustfs★ 36ksame name
- dotnet/maui★ 23ksame name
- NVIDIA/Megatron-LM★ 18ksame name
- MiniMax-AI/skills★ 14ksame name
- btriapitsyn/openchamber★ 13ksame name
- 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 repository20 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- product/CLAUDE.mdCLAUDE.md
- pulse-web-otel/CLAUDE.mdCLAUDE.md
- add-ai-sub-agentSkill
- add-alert-metricSkill
- add-api-endpointSkill
- add-ui-componentSkill
- add-ui-screenSkill
- clickhouse-migrationSkill
- deploy-serviceSkill
- fatal-fiveSkill
- integrate-pulse-web-sdkSkill
- pulse-prd-authorSkill
- pulse-prd-reviewSkill
- web-otel-spec-audit-orchestratorSkill
- web-otel-spec-implementation-auditSkill
- web-sdk-e2e-matrixSkill
- web-sdk-instrumentSkill
- web-sdk-shipSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 180 edited versions we read keep these.
2
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
- Distinctive: line 19
Use one of the following. Prefer MCP when it is connected and healthy.
- Very specific: line 23
Read the MCP tool schemas in the Cursor mcps folder, then call the documented tools.
- Distinctive: line 39
Follow the prompts: GitHub.com vs Enterprise, HTTPS vs SSH, then either “Login with a web browser” or “Paste an authentication token.”
- Very specific: line 78
If gh prints 401 or 403, complete gh auth login or refresh SSO (gh auth refresh -h github.com with -s scopes if needed).
- Very specific: line 80
After fetching, proceed to Step 2 using the same review checklists whether data came from MCP or gh.
“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.
Files
PR Review Workflow
Workflow
- [ ] Step 1: Fetch PR details (MCP or gh — see below)
- [ ] Step 2: Review diff by area
- [ ] Step 3: Check cross-cutting concerns
- [ ] Step 4: Provide structured feedbackStep 1: Fetch PR Details
Use one of the following. Prefer MCP when it is connected and healthy; otherwise use GitHub CLI in the project repo (or any cwd) with a logged-in user.
Option A: GitHub MCP (when available)
Read the MCP tool schemas in the Cursor mcps folder, then call the documented tools. Typical names:
get_pull_request— title, description, author, base/head branchesget_pull_request_files— list of changed filesget_pull_request_diff— full diff
Option B: GitHub CLI (gh)
Requires GitHub CLI installed and authenticated (gh auth status succeeds).
One-time login (interactive):
gh auth loginFollow the prompts: GitHub.com vs Enterprise, HTTPS vs SSH, then either “Login with a web browser” or “Paste an authentication token.”
Credentials you need:
| Method | What you use |
| Web browser | Your normal GitHub account sign-in (SSO/org access if the org requires it). No manual token copy if you use the browser flow. |
| Personal Access Token (HTTPS) | A classic PAT with at least repo (private repos), or a fine-grained token with Repository access to the target repo and permissions: Contents Read, Metadata Read, Pull requests Read. |
Verify:
gh auth statusFetch PR metadata and changed files (replace OWNER, REPO, N):
gh pr view N --repo OWNER/REPO --json title,body,author,baseRefName,headRefName,state,commits,filesFull diff (patch):
gh pr diff N --repo OWNER/REPOList file names only:
gh pr view N --repo OWNER/REPO --json files --jq '.files[].path'Checkout the PR branch locally (optional, for git inspection):
gh pr checkout N --repo OWNER/REPOIf gh prints 401 or 403, complete gh auth login or refresh SSO (gh auth refresh -h github.com with -s scopes if needed).
After fetching, proceed to Step 2 using the same review checklists whether data came from MCP or gh.
Step 2: Review by Area
Backend Changes (backend/)
- Service interface + impl pattern
- ServiceError used for errors (not raw exceptions)
- SQL in Queries class (not inline)
- RxJava types (Single, Maybe, Completable)
- MapStruct mapper (not manual mapping)
- Lombok annotations on DTOs
- Tests with >80% coverage on changed code
- Checkstyle: 140 char lines, 2-space indent
Frontend Changes (pulse-ui/)
- Screen folder convention followed
- Mantine components (not raw HTML)
- TanStack Query for server state
- makeRequest for API calls
- Types in .interface.ts files
- CSS modules (not inline styles)
AI Agent Changes (pulse_ai/)
- FunctionTool pattern with ToolContext
- STATE_KEYS for state (not strings)
- Registry entries (not hardcoded)
- SQL safety enforced
Deploy Changes (deploy/)
- Health check included
- Dependencies with service_healthy condition
- .env.example updated for new vars
- No secrets in committed files
Step 3: Cross-Cutting
- Alert metric changes → all 5 layers updated?
- New env vars → added to
.env.example? - New API endpoints → DTO + service + DAO + mapper + tests?
- Security: no secrets, keys, or credentials in code?
Step 4: Feedback Format
## Review Summary
### Critical (must fix)
- ...
### Suggestions (should improve)
- ...
### Nice to Have (optional)
- ...Include specific file:line references and code examples for fixes.
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
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.

