A tool for taking an existing GitHub pull request—the proposed change submitted for review—and getting it ready to merge by handling review comments, security findings, conflicts, and failed checks.

It helps finish one pull request, every open pull request in a repository, or every open pull request across an organisation. It also handles pull requests created by bots.

It removes the need to repeatedly monitor several sources of feedback and fix each problem by hand before a pull request can be merged.

finalize-pr — Skill by dryvist

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.

agentmods

npx agentmods add skills/dryvist/claude-code-plugins/finalize-pr

Any agent

npx skills add dryvist/claude-code-plugins --skill finalize-pr

Clone the repo

git clone --depth 1 https://github.com/dryvist/claude-code-plugins

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,583 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00063	$0.03583
Opus 5	$0.00032	$0.01792
Sonnet 5	$0.00013	$0.00717
Haiku 4.5	$0.00006	$0.00358

Measured yesterday against content hash 56b11970f719, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

finalize-pr 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 yesterday.

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.

github-workflows/skills/finalize-pr/SKILL.md · 293 lines

How it starts

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

Finalize PR

FULLY AUTOMATIC - Fully automates PR finalization: monitor, fix, prepare for merge. Assumes PR already exists. No manual intervention required. For manual review-focused workflows, use /review-pr.

State warning: Automated reviewers (CodeQL, Copilot, AI reviews) post asynchronously. CI may have re-run. Merge conflicts may have appeared. Re-fetch live PR state from Step 1.

Critical Rules

Verify all checks pass via Phase 3 gate - Re-run Phase 3 against live API on every invocation; "mergeable" means git-conflict-free only, not fully unblocked.
Resolve all conversations - Automatically invoke /resolve-pr-threads for review threads
Fix all CodeQL violations - Check repository and automatically fix using /resolve-codeql
Simplify all code changes - Invoke /simplify at Step 2.3.5 (after all fixes). Pre-push simplification is handled by /ship.
Validate locally before pushing - Run project linters and tests
Monitor CI early, block last - Start CI monitoring in background immediately, but fix other issues while it runs
Update PR metadata automatically - Before reporting ready, update title, description, and linked issues via haiku subagent
Take direct action - Identify issues and fix them automatically
Include bot PRs - Never filter by author. All modes include dependabot, release-please, claude, github-actions, etc.
Never cross org boundaries - Org mode derives owner from current repo only
Git Flow Promotion - For Git Flow repositories, after merging the PR into develop and validating it, you must ensure a release promotion to main is triggered via /promote-release as a mandatory, non-optional step. You must add this task to the active session checklist.

Phase 1: PR Discovery and Targeting

Steps 1.1–1.4 run sequentially.

1.1 Parse Argument

Argument	Mode	Target
(none)	Current branch	Single PR on current branch
`42`	Single PR	PR #42
`all`	Repo-wide	All open PRs in current repo
`org`	Org-wide	All open PRs across all repos in current org

Read the full file on GitHub · 293 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.

yesterday First seen · 293 lines · 63 tokens per session scan A 56b11970f719

Subscribe to this mod's changes

finalize-pr is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 3,583 once invoked, about $0.0003 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 review Git and workflow Security ai-tools anthropic automation claude claude-code claude-plugins

rspec

This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…

hoblin/claude-ruby-marketplace · 125 tokens

activerecord

This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…

hoblin/claude-ruby-marketplace · 180 tokens

draper-decorators

This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…

hoblin/claude-ruby-marketplace · 131 tokens

mcp-server

This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…

hoblin/claude-ruby-marketplace · 98 tokens

ratatui-ruby

This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…

hoblin/claude-ruby-marketplace · 119 tokens

dragonruby

This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…

hoblin/claude-ruby-marketplace · 100 tokens