pr-ready

pr-ready is a skill for Claude Code, Codex from OutThisLife/brooklyn-skills. It costs 74 tokens per session (2,091 once invoked), scanned A, original, MIT.

A workflow for making an existing pull request or merge request ready to merge. It updates the branch from the default branch, fixes relevant build checks, and handles open review comments.

In plain words
What is it for?
Use it when asked to rebase a change, fix its CI/CD checks, address human or automated review comments, or make it mergeable. It helps inspect each blocker, apply the needed fix, and check again.
Why use it?
It removes common merge blockers such as an outdated branch, failing continuous integration checks, or unresolved reviewer discussions. It keeps the work limited to what is needed for that request.

Skill for Claude CodeCodex

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

Good fit Use it when asked to rebase a change, fix its CI/CD checks, address human or automated review comments, or make it mergeable. It helps inspect each blocker, apply the needed fix, and check again.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outthislife/brooklyn-skills/pr-ready
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 OutThisLife/brooklyn-skills --skill pr-ready
Clone the repo
git clone --depth 1 https://github.com/OutThisLife/brooklyn-skills

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-ready

README.md
[![agentmods](https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/pr-ready/github.svg)](https://agentmods.dev/skills/outthislife/brooklyn-skills/pr-ready)
Your own site
<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/pr-ready"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/pr-ready/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-ready

Your own site · 80×15
<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/pr-ready"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/pr-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,091 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00074 $0.02091
Opus 5.5 $0.00030 $0.00836
Sonnet 5.5 $0.00015 $0.00418
Haiku 4.5 $0.00007 $0.00209

Measured 1mo ago against content hash 3ea5cd4a1b57, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-ready 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 1mo 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-ready/SKILL.md · 109 lines

How it starts

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

PR Ready

An open PR/MR isn't mergeable. Two things block it — a stale base or red CI, and open review threads. Same loop for both: fix, push, re-query the forge, repeat. Handle whichever is blocking; usually that's both.

No feature work. No drive-bys.

Rebase + CI

  1. Find the worktree for this PR (or create one per repo convention). Prefer an existing worktree the user already has.
  2. git fetch origin <default> (usually main).
  3. Honor repository history rules before choosing an update strategy. Where force pushes are forbidden or the user requires a merge, merge origin/<default> into the existing branch without rewriting commits. Otherwise rebase onto origin/<default>. Resolve conflicts by reading both sides' intent and regression tests; shared callback code must preserve newer callback-once behavior as well as the PR's guards.
  4. Push (--force-with-lease if the rebase rewrote history).
  5. Watch CI. Fix failures caused by the rebase or existing breakage on this branch — nothing else.
  6. Flaky upstream on the default branch → say so. Don't paper over it with unrelated test deletes.
  7. Verify process.execPath in the same execution mode as MR tests, using the repository's package manager. Background login shells can replace an earlier PATH export, so select the project's declared Node version inside the launched command. A newer runtime can shadow happy-dom localStorage or remove util.isDate; rerun unchanged failing tests under the supported runtime before editing application code.
  8. For merge commits, old lint-staged hooks can autoformat every upstream file in the index. Run lint on the PR delta and the repository precommit checks explicitly, preserve upstream files, and document any one-command hook bypass used solely to prevent unrelated formatting. Never call that bypass a substitute for verification. Do not assume HUSKY_SKIP_HOOKS=1 is honored: inspect the hook output. Legacy hook git add can also include unstaged edits to already-staged files. Reconcile the resulting commit against the pre-merge PR file set plus intended fixes, and restore unrelated suppression-file pruning rather than publishing incidental changes.

Read the full file on GitHub · 109 lines

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. 1mo ago Changed · +34 lines 3ea5cd4a1b57
  2. 2mo ago First seen · 75 lines · 74 tokens per session scan A ccd5f8bf3a1d

Subscribe to this mod's changes

pr-ready is a skill published in the GitHub repository OutThisLife/brooklyn-skills (209 stars, last pushed 7d ago), licensed MIT. It adds 74 tokens to every session and 2,091 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens