agentleFS
polyaipolyai/adk/.claude/skills/review-pr/SKILL.md

review-pr

Skill83 starsChanged 41 days agoApache-2.0View on GitHub

Review an ADK pull request or local branch against the repo's review checklist (REVIEW.md) and report blocking issues and nits. Use when asked to review a PR in the polyai-adk repo, or to self-review a branch before opening one.

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

  • 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

    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

  • 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

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 178 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:

    Read REVIEW.md at the repo root and apply every item to the diff, the PR title and the description.

    line 13
  2. Distinctive:

    Check the claims against the code.

    line 16
  3. Very specific:

    If you're asked to post the review, use gh pr review <number> with the report as the body, and only after the user confirms.

    line 27

“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 an ADK change

  1. Get the change.
    • A PR: gh pr view <number> for the title and description, and gh pr diff <number>.
    • A local branch: git log --oneline main..HEAD and git diff main...HEAD.
  2. Read REVIEW.md at the repo root and apply every item to the diff, the PR title and the description. For anything that touches resources or commands, also read src/poly/resources/AGENTS.md or src/poly/cli_commands/AGENTS.md.
  3. Check the claims against the code. Open the files around each change before flagging it, and drop anything you can't point to a line for.
  4. Skip everything on REVIEW.md's ignore list.

Report

  1. Summary: what the change does, in one or two sentences.
  2. Blocking: each issue with file:line, what's wrong and the fix.
  3. Worth raising and nits, in the same format and kept short.
  4. Verdict: approve, request changes or comment.

If you're asked to post the review, use gh pr review <number> with the report as the body, and only after the user confirms.

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.