agentmods.dev

pr-factory-pipeline

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

A coordinator that runs several pull-request preparation stages in order, from codebase exploration through review and writing the pull-request text.

In plain words
What is it for?
It is for preparing one or more pull requests in full, quick-win, or architecture-focused workflows, with optional focus on areas such as tests, documentation, performance, or refactoring.
Why use it?
It removes the need to manually manage handoffs between separate analysis, implementation, and review stages.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

not rated 2repo 3mo ago A scan 98 tokens original MIT

Good fit It is for preparing one or more pull requests in full, quick-win, or architecture-focused workflows, with optional focus on areas such as tests, documentation, performance, or refactoring.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atman36/codex-maintainer-kit/pr-factory-pipeline
View source ↗ Atman36/codex-maintainer-kit
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-pipeline
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-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-pipeline.svg)](https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-pipeline)
Your own site
<a href="https://agentmods.dev/skills/atman36/codex-maintainer-kit/pr-factory-pipeline"><img src="https://agentmods.dev/badge/skills/atman36/codex-maintainer-kit/pr-factory-pipeline.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,376 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.00098 $0.01376
Opus 5 $0.00049 $0.00688
Sonnet 5 $0.00020 $0.00275
Haiku 4.5 $0.00010 $0.00138

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

Security

Grade A, and why

pr-factory-pipeline 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 8d 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-pipeline/SKILL.md · 133 lines

How it starts

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

Role: Pipeline Orchestrator

Coordinate the PR Factory sequence and hand off outputs between stages.

skills are instructions, not shell commands. For deterministic automation use ../../tools/run_pipeline.py with explicit --stage-command values.

Inputs

  • {{REPO_ROOT}} - Absolute path to target repository (can be outside current workspace)
  • {{REPO_URL}} - Repository URL (optional but preferred)
  • {{BASE_BRANCH}} - Base branch (default: main)
  • {{CONTEXT_PATH}} - Optional path to external context (deepresearch/ directory or a single .md file)
  • {{FOCUS}} - Optional focus (docs|tests|bugfix|perf|refactor|ci|dx)
  • {{MODE}} - Optional mode (full|quick-win|architecture)
  • {{MAX_PRS}} - Optional max PR count for Gatekeeper (default: 1)
  • {{RUNNER}} - Optional runner (auto|task|cli, default: auto)

Mode Selection

  • full (default):
    • Analysis once: scout -> analyst -> critic -> gatekeeper
    • Then per PRSpec: implementer -> reviewer -> pr-writer -> (publisher if requested)
  • quick-win:
    • Analysis once: scout -> gatekeeper
    • Then per PRSpec: implementer -> reviewer -> pr-writer -> (publisher if requested)
  • architecture:
    • Analysis once: architect -> critic -> gatekeeper
    • Then per PRSpec: implementer -> reviewer -> pr-writer -> (publisher if requested)

Detailed per-stage contracts: references/stage-contracts.md.

Process

  1. Normalize inputs and select mode.
    • For automation, use deterministic orchestration via ../../tools/run_pipeline.py.
    • Select runner: auto (default fallback), task, or cli.
  2. If CONTEXT_PATH is provided:
    • read only relevant files (prefer .md summaries),
    • extract constraints/policies/risk notes,
    • pass concise context forward to Analyst/Critic/Gatekeeper.
  3. Run mandatory preflight and fail fast on infra/runtime issues.
  4. Run analysis stages once and collect JSON output.
  5. Feed output JSON into the next stage placeholders.
    • If stage returns SAVED_JSON_PATH=..., read JSON from that file and continue handoff.
  6. Enforce gates before moving forward:
    • Critic decision must be approve.
    • Gatekeeper decision must be pr.
  7. Extract pr_specs[] from Gatekeeper (data.pr_specs preferred; fallback to pr_spec).
  8. For each PRSpec run implementer -> reviewer -> pr-writer (and publisher if requested).
    • Keep fail/retry isolation per PRSpec.
    • Continue processing other PRSpecs even if one fails.
  9. Before publish, run readiness checks and base-drift guard.
  10. Return pipeline result with:
  • per-stage summary,
  • per-PR status array,
  • selected runner,
  • machine-readable summary path.

Read the full file on GitHub · 133 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. 8d ago First seen · 133 lines · 98 tokens per session scan A e956be984056

Subscribe to this mod's changes

pr-factory-pipeline is a skill published in the GitHub repository Atman36/codex-maintainer-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 98 tokens to every session and 1,376 once invoked, about $0.0005 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.

Code reviewGit and workflowai-agentsautomationcodexcodex-clideveloper-tools
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