finish-pr

Original：🇺🇸 English

Translated

Move completed local GitHub issue work to a ready-for-merge pull request. Use when development is complete, the user says finish PR, publish this branch, open a ready PR, or an agent has objective evidence the branch is ready for review.

3installs

Sourcepatinaproject/skills

Added on2026-05-19

NPX Install

npx skill4agent add patinaproject/skills finish-pr

SKILL.md Content

View Translation Comparison →

Finish PR

Quick Start

When local work is complete, follow workflows/ready-for-merge.md.

Example: on branch

42-let-agents-use-github-more-ergonomically

, infer issue

#42

, verify the diff, commit as

feat: #42 ...

, push, and create or update the ready-for-review PR.

This skill verifies, commits, pushes, creates or reuses a ready-for-review pull request, then loops through checks and PR feedback until the PR is ready-to-merge or human input is required. It never merges the PR.

Workflow

Read repository guidance, commit rules, and the PR template.
Infer the issue from the current branch or existing PR metadata; ask if ambiguous.
Inspect uncommitted changes and stage only relevant paths.
Run the repository's documented verification commands.
Commit using the repository's required commit format.
Push the branch when there is work to publish.
Create or update a ready-for-review PR using the repository template.
Enter the readiness loop: watch all checks, triage every problematic check and PR feedback item, fix branch-local issues, push, and repeat.
Mark draft PRs ready when the loop reaches the ready state.
Report ready-to-merge status without merging.

Guardrails

Do not rewrite branch history or force-push by default.
Do not create follow-up issues from PR feedback.
Do not wait indefinitely for new human review comments.
Do not use fail-fast or required-check-only watching by default.
Do not add AI or agent attribution unless the repository requires it.
Stop for secrets, permissions, product decisions, or ambiguous scope.