review-pr
Skill236 starsChanged 8 months agoApache-2.0View on GitHub
Review a pull request against arksim project standards
185 other projects use a version of this.
Adopted by
Most recently taken up by
- torrust/torrust-trackertheir own version, first seen Nov 16, 2026
- Wendor/teapod-streamtheir own version, first seen Nov 16, 2026
- testcontainers/testcontainers-javatheir own version, first seen Nov 16, 2026
- hotcodepush-team/skillstheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- ayoubben18/ab-methodtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use diagnose-ci-failures, review-delta 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-labSkilldiagnose-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
n24q02mSkillreview-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
GeiserXSkilldocs-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
GeiserXSkillfull-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
n24q02mSkillbuild-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
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- denoland/deno★ 109ksame name
- ToolJet/ToolJet★ 41ksame name
- remix-run/remix★ 33ksame name
- tirth8205/code-review-graph★ 33ksame name
- alpinejs/alpine★ 32ksame name
- nrwl/nx★ 29ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- livewire/livewire★ 24ksame name
- microsoft/fluentui★ 20ksame name
175 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- draft-prSkill
- pre-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
0
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
- Very specific: line 46
If behavior, config, or API changed, verify docs/ updates
- Very specific: line 47
Check for CHANGELOG.md entry under [Unreleased]
“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.
Files
Review PR
Review an open pull request for functional correctness and project conventions. Focus on logic, architecture, and behavior. Formatting issues are caught by CI (ruff, pre-commit) and do not need manual review.
Steps
- Fetch PR metadata and diff
gh pr view $ARGUMENTS --json title,body,files,additions,deletions,commits,headRefName gh pr diff $ARGUMENTS - Validate PR title and description
- Title matches Conventional Commits regex, under 72 chars
- Description has 20+ characters of real content
- These are also CI-enforced, so flag only if CI somehow missed them
- Review functional changes
Focus on:
- Logic correctness: does the code do what the PR claims?
- Edge cases: are error paths handled?
- API changes: are they backwards compatible or properly marked as breaking?
- Security: no hardcoded secrets, no unsanitized input in dangerous contexts
- Performance: any obvious inefficiencies (N+1 queries, unbounded loops)?
- Check scope
- Single concern per PR
- Flag unrelated changes bundled together
- Check test coverage
- New behavior should have tests
- Flag large additions to
arksim/with no corresponding test changes
- Check documentation
- If behavior, config, or API changed, verify
docs/updates - Check for CHANGELOG.md entry under
[Unreleased]
- If behavior, config, or API changed, verify
- Check license headers on new files
- New
.pyfiles should start with# SPDX-License-Identifier: Apache-2.0
- New
Output
| Check | Status | Notes |
| Title format | PASS/FAIL | ... |
| Description | PASS/FAIL | ... |
| Functional correctness | PASS/WARN | ... |
| Scope | PASS/WARN | ... |
| Tests | PASS/WARN | ... |
| Docs/Changelog | PASS/WARN | ... |
| License headers | PASS/N/A | ... |
End with: APPROVED, CHANGES REQUESTED, or NEEDS DISCUSSION.
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.

