agentleFS
arklexaiarklexai/arksim/.claude/skills/review-pr/SKILL.md

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

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-labSkill

    diagnose-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

  • n24q02mSkill

    review-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

  • GeiserXSkill

    docs-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

  • GeiserXSkill

    full-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

  • n24q02mSkill

    build-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

    1. denoland/deno★ 109ksame name
    2. ToolJet/ToolJet★ 41ksame name
    3. remix-run/remix★ 33ksame name
    4. tirth8205/code-review-graph★ 33ksame name
    5. alpinejs/alpine★ 32ksame name
    6. nrwl/nx★ 29ksame name
    7. PrefectHQ/fastmcp★ 29ksame name
    8. jlowin/fastmcp★ 29ksame name
    9. livewire/livewire★ 24ksame name
    10. 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.

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
  1. Very specific:

    If behavior, config, or API changed, verify docs/ updates

    line 46
  2. Very specific:

    Check for CHANGELOG.md entry under [Unreleased]

    line 47

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Fetch PR metadata and diff
    gh pr view $ARGUMENTS --json title,body,files,additions,deletions,commits,headRefName
    gh pr diff $ARGUMENTS
  2. 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
  3. 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)?
  4. Check scope
    • Single concern per PR
    • Flag unrelated changes bundled together
  5. Check test coverage
    • New behavior should have tests
    • Flag large additions to arksim/ with no corresponding test changes
  6. Check documentation
    • If behavior, config, or API changed, verify docs/ updates
    • Check for CHANGELOG.md entry under [Unreleased]
  7. Check license headers on new files
    • New .py files should start with # SPDX-License-Identifier: Apache-2.0

Output

CheckStatusNotes
Title formatPASS/FAIL...
DescriptionPASS/FAIL...
Functional correctnessPASS/WARN...
ScopePASS/WARN...
TestsPASS/WARN...
Docs/ChangelogPASS/WARN...
License headersPASS/N/A...

End with: APPROVED, CHANGES REQUESTED, or NEEDS DISCUSSION.

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.