pr-factory-reviewer

pr-factory-reviewer is a skill for Claude Code, Codex from Atman36/codex-maintainer-kit. It costs 71 tokens per session (647 once invoked), scanned A, original, MIT.

A post-implementation review for checking a proposed pull request before it is written. A pull request is a request to merge code changes into a shared codebase.

In plain words
What is it for?
It compares the actual Git changes with the approved change scope, checks diff cleanliness and test evidence, and returns a pass, retryable fixes, or a request for human input.
Why use it?
It catches out-of-scope files, debug code, accidental artifacts, and missing test evidence before review reaches maintainers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It compares the actual Git changes with the approved change scope, checks diff cleanliness and test evidence, and returns a pass, retryable fixes, or a request for human input.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atman36/codex-maintainer-kit/pr-factory-reviewer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Atman36/codex-maintainer-kit --skill pr-factory-reviewer
Clone the repo
git clone --depth 1 https://github.com/Atman36/codex-maintainer-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pr-factory-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-reviewer/github.svg)](https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-reviewer)
Your own site
<a href="https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-reviewer"><img src="https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pr-factory-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-reviewer"><img src="https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.00647
Opus 5 $0.00036 $0.00324
Sonnet 5 $0.00014 $0.00129
Haiku 4.5 $0.00007 $0.00065

Measured 9d ago against content hash 892a4d85f790, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

pr-factory-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pr-factory-reviewer/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role: Reviewer (Post-Implementation Gate)

Review the implemented diff as a maintainer would, before PR Writer.

Inputs

  • {{REPO_ROOT}} - Workspace path
  • {{PRSPEC_JSON}} - Approved PRSpec (scope contract)
  • {{IMPLEMENT_JSON}} - Implementer output JSON
  • {{DIFF_SUMMARY}} - Optional diff summary (git diff --name-status, git diff --stat)

Goal

Ensure the actual diff is minimal, clean, and aligned with PRSpec before creating the final PR message.

Process

  1. Compare changed files vs the PRSpec files_touched list.
  2. Check for hygiene issues (debug prints, commented dead code, accidental artifacts).
  3. Verify tests/commands evidence from Implementer output.
  4. Return pass/fail with explicit required fixes.

For detailed checks, see references/review-checklist.md.

Rules

  • Be strict on scope creep and noisy diffs.
  • If issue is fixable by Implementer, return status=retryable with concrete actions.
  • If issue needs human product/architecture decision, return status=needs_human.
  • Output JSON only (ExecutionResult).

Output Format

Return JSON conforming to ../../schemas/execution_result.schema.json with:

{
  "schema_version": "1.0",
  "id": "reviewer-<timestamp>",
  "stage": "reviewer",
  "status": "success",
  "summary": "Diff is clean and aligned with PRSpec",
  "started_at": "2026-02-13T00:00:00Z",
  "finished_at": "2026-02-13T00:01:00Z",
  "exit_code": 0,
  "artifacts": [],
  "metrics": {
    "duration_ms": 60000,
    "cost_usd": 0.0,
    "tokens_in": 0,
    "tokens_out": 0
  },
  "errors": [],
  "warnings": [],
  "data": {
    "decision": "pass",
    "required_fixes": [],
    "findings": [],
    "scope_check": {
      "files_touched_declared": ["src/utils/validation.test.ts"],
      "files_changed_actual": ["src/utils/validation.test.ts"],
      "unexpected_files": []
    }
  }
}

Quality Standards

  • Reject diff if unexpected files exist and were not justified.
  • Reject diff if obvious debug leftovers exist (console.log, print, TODO noise).
  • Require specific fix instructions, not generic complaints.

Read the full file on GitHub · 87 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 87 lines · 71 tokens per session scan A 892a4d85f790

Subscribe to this mod's changes

pr-factory-reviewer is a skill published in the GitHub repository Atman36/codex-maintainer-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 647 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

docs-release-notes

Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…

The01Geek/prflow · 106 tokens

docs-sync-internal

Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…

The01Geek/prflow · 105 tokens

pr-description

Use when generating or updating a PR description for the current branch. Takes an optional issue number as argument.

The01Geek/prflow · 24 tokens

retrospective-audit

Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…

The01Geek/prflow · 91 tokens

openclaw-github-dedupe

Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.

vincentkoc/dotskills · 68 tokens

docs

Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…

The01Geek/prflow · 97 tokens