agentleFS
Sign inStart free
shiranjitshiranjit/agentic-primer/skills/pr-gate/SKILL.md

pr-gate

Skill1 starsChanged 4 months agoMITView on GitHub

Mandatory review gate for every pull request. Use this skill whenever a PR is created, whenever code is about to be merged or promoted between branches (feature→dev, dev→release, release→production), and whenever anyone asks for a code review. No PR merges in this project without this gate returning GO.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. monsieurBelbo/claude-skills★ 0same name

    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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every PR is reviewed by an advisor agent through the project's defined lens — our standards, not generic instincts.

    line 9
  2. Distinctive:

    When uncertain, the advisor's verdict is NO-GO.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

PR Gate Skill

Purpose

Every PR is reviewed by an advisor agent through the project's defined lens — our standards, not generic instincts. The human Leader supervises the standards; the advisor applies them tirelessly to every diff.

Protocol

  1. Assemble the lens. Load the following skills and pass them to the reviewer as its review criteria: architecture, gitflow, documentation, plus any feature-area skills touched by the diff.
  2. Spawn an advisor agent with: the diff, the linked plan/handoff, and the lens. The advisor has no authoring context — it judges only what is in front of it.
  3. The advisor reviews against the checklist below and returns a verdict: GO or NO-GO with cited items.
  4. On NO-GO: the authoring agent fixes and resubmits. Do not argue the verdict; fix or escalate to the Leader.
  5. On GO: merge may proceed per the gitflow skill. For release→production, GO is necessary but not sufficient — Leader approval is still required.
  6. Record the verdict (GO/NO-GO, advisor's key findings) in the PR description.

Review checklist (the advisor's lens)

Correctness & tests

  • TDD evidence: tests exist, were written for the behavior, and pass.
  • Coverage: test cases genuinely cover the feature's cases, including error paths. Flag thin coverage explicitly.
  • Golden test data updated if new cases were discovered.

Architecture

  • Complies with the architecture skill (client/server split, state machines, migrations-only, contract documented).

Safety

  • No deletes/renames of shared branches, no force-push, no history rewrite.
  • No credentials, tokens, keys, or secrets in code, config, tests, or docs.
  • No destructive data operations (DROP, TRUNCATE, mass DELETE) outside a reviewed migration.

Scope & hygiene

  • Diff matches the plan/handoff; no unrelated drive-by changes.
  • Documentation updated per the documentation skill (capability docs, release notes as applicable).

Failure stance

When uncertain, the advisor's verdict is NO-GO. A false stop costs minutes; a false pass costs production.

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.

Check your setup, free