agentleFS
ThinkFlowLabThinkFlowLab/agentdescent/.claude/skills/review-pr/SKILL.md

review-pr

Skill203 starsChanged 7 days agoMITView on GitHub

Review an AgentDescent PR (or local change) at a tip SHA and write a Verifier report with Tip SHA / Ran / Not run / Verdict PASS|FAIL|INC that the review gate can read.

  • Reads credentials
  • Installs packages

185 other projects use a version of this, 2 of them edited.

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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read the rules from origin/main, not a stale copy: AGENTS.md, CODE_STANDARDS.md, LESSONS.md, and this file (git show …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 177 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

AgentDescent review-pr

Produces a Verifier report for ThinkFlowLab/agentdescent. The report is evidence, not merge authority: what may happen after a PASS is AGENTS.md › Merge policy.

Establish the tip

  1. Work in a fresh clone (git clone https://github.com/ThinkFlowLab/agentdescent), check out the PR head (gh pr checkout <n>), record git rev-parse HEAD. If the head moves during the review, start over.
  2. Read the rules from origin/main, not a stale copy: AGENTS.md, CODE_STANDARDS.md, LESSONS.md, and this file (git show origin/main:.claude/skills/review-pr/SKILL.md).
  3. Inventory the diff against the merge base (git diff origin/main...HEAD --stat) and get the tier: python3 .github/scripts/risk_gate.py --pr <n>. The PR description is narrative, not evidence.

Re-run the gates yourself

pip install -e ".[dev,mcp]"
pytest -q                               # the whole suite, not only the new tests
python -m tools.gen_api_docs --check    # when agentdescent/__init__.py or a public signature changed
python -m tools.changelog_fragments check
mkdocs build --strict                   # when docs/ or mkdocs.yml changed (needs .[docs])
  • Fails on main: copy only the new/changed test files onto the merge base and run them; they must fail there and pass at the tip.
  • Ark real-model checks only when the change touches a model path and ARK_API_KEY is already in the environment; otherwise list them under Not run:.

Instant FAIL

  • A key, token or credential anywhere in the diff.
  • A network or model call reachable from pytest -q.
  • docs/api.md edited by hand or out of sync; CHANGELOG.md edited in a PR.
  • A claimed fix with no test that fails on main.
  • An unconditional @pytest.mark.skip / xfail hiding a failure.
  • A port that departs from its source's released code without saying so.

Verdicts

VerdictMeaning
PASSNo actionable findings; every gate you list under Ran: was run by you at this tip and is green
FAILAn actionable defect (correctness, a hard rule, a missing fail-on-main test, a dishonest claim)
INCIncomplete: a material check not run, the tip moved, scope unclear. INC is not PASS

Report shape (the review gate parses this)

Post it as one PR comment from the Birfy login (self-review counts). Keep the block intact; the last Tip SHA: block in the comment is the one read, the newest report at a tip wins, and a PASS without a Ran: entry or without a Not run: line does not count.

Self-review (Birfy)

Tip SHA: <full 40-hex head>
Ran:
  - pytest -q → pass (<N> passed, <M> skipped)
  - python -m tools.gen_api_docs --check → pass
  - CI at this tip → green (build, test 3.9-3.13)
Not run:
  - Ark real-model run — no model path changed
Findings:
  - none
Verdict: PASS

Then check it counts: python3 .github/scripts/review_gate.py --pr <n>.

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.