finalize-prs

Scans open pull requests and finalizes unfinished ones via the finalize-pr skill.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill finalize-prs-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finalize-prs
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/finalize-prs
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill finalize-prs-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping track of multiple open pull requests across repositories is tedious, and unfinished ones (unresolved review threads, failing CI, divergence from the base branch) easily slip through. This Skill scans all of your open PRs, determines which ones are actually incomplete, and finishes them one by one. ## Core Features & Use Cases - Cross-repository PR scanning: Collects your open PRs with gh pr list --author "@me", either for one named repository or across all locally cloned repositories. - Completion judgment: Checks each PR for unresolved review threads, genuine CI failures (distinguishing real failures from skipped checks or approval waits), divergence from the base branch, and merge conflicts. - Sequential finalization: Delegates each unfinished PR to the finalize-pr skill one at a time, avoiding branch-checkout conflicts, then returns to the original branch and reports a full audit table. - Use Case: Before ending your week, ask the assistant to check all your open PRs; it finds two with unresolved review comments and one with a failing CI job, fixes each via finalize-pr, and reports what was done without marking anything ready for review. ## Quick Start Ask the assistant to check all of my open pull requests and finish any that are incomplete.

Frequently Asked Questions about finalize-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finish all my open GitHub pull requests at once?

Invoke the skill with no arguments to scan every locally cloned repository, or pass a repository name to scope it. It lists your open PRs with gh pr list, judges completeness, and delegates unfinished ones to the finalize-pr skill sequentially.

What counts as an unfinished pull request in this scan?

A PR is unfinished if it has unresolved review threads, genuinely failing CI checks, divergence from the base branch that would break on integration, or a CONFLICTING mergeable state. Skipped checks and approval-waiting statuses are not treated as failures.

Does it process draft pull requests or mark PRs as ready?

Draft PRs are included if they are incomplete, since readiness is separate from completeness. The skill never marks PRs as ready; it only finishes the work and leaves the ready-for-review decision to the user.

Why does the skill stop when the working tree is dirty?

It checks out different branches while finalizing PRs, so uncommitted changes would be carried across branches. If git status --porcelain is not empty, it reports the situation and exits before doing anything.

Can it finalize pull requests in parallel across repositories?

No. Finalization runs strictly one PR at a time because each involves a git checkout, and parallel runs would corrupt each other's working trees. If one PR fails, the skill stops and reports where it halted.

Does it touch pull requests authored by other people?

No. It only targets PRs authored by you, filtered with gh pr list --author "@me". Reviewing or fixing other people's PRs is explicitly out of scope and belongs to a separate review workflow.