Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it.
Install Finish PR
$ npx skills add stella/stella --skill finish-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stella/stella finish-pr --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/finish-pr .claude/skills/finish-pr && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .claude/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stella/stella/tree/main/.agents/skills/finish-prType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stella/stella --skill finish-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stella/stella finish-pr --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/finish-pr .agents/skills/finish-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .agents/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stella/stella --skill finish-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stella/stella finish-pr --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/finish-pr .cursor/skills/finish-pr && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .cursor/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stella/stella.git --path .agents/skills/finish-pr--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stella/stella --skill finish-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stella/stella finish-pr --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/finish-pr .gemini/skills/finish-pr && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .gemini/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stella/stella finish-prInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stella/stella --skill finish-pr -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/finish-pr .github/skills/finish-pr && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .github/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stella/stella --skill finish-pr -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stella/stella finish-pr --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stella/stella.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/finish-pr .opencode/skills/finish-pr && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "finish-pr" agent skill from https://github.com/stella/stella/tree/main/.agents/skills/finish-pr into .opencode/skills/finish-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finish-pr", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
finish-pr- GitHub stars
- 258
- Token cost
- ~1.1k tokens
- SKILL.md length
- 655 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it.
- Works in 4 steps: Establish Authority and Isolation → Review Independently → Converge Reviews and CI → …
- Explicitly requests it
- SKILL.md covers 1. Establish Authority and…, 2. Review Independently, 3. Converge Reviews and CI and 4. Stop at a Real Terminal State
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Finish PR is an agent skill from stella/stella. Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: Open-source legal workspace. The licence is Apache-2.0.
When your agent uses it
- Explicitly requests it
- Tasks that involve Pull requests
Example prompts
- “/finish-pr”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b225fd8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Finish PR loads about 1.1k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 655 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from stella/stella at commit b225fd8, republished under its Apache-2.0 licence (© stella). 655 words, ~1,118 tokens.
Download SKILL.mdSave it as
.claude/skills/finish-pr/SKILL.md (or your agent's skills folder).- name
- finish-pr
- description
- Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it.
Finish PR
Bring an existing pull request to a current-head state that is reviewable or mergeable. This is a convergence workflow: repeat review and validation until a terminal condition is reached.
1. Establish Authority and Isolation
Resolve the PR, repository, branch, current head SHA, base branch, draft state, required checks, review state, and applicable repository instructions. Work from a clean isolated checkout of the PR head. Preserve unrelated changes.
Pin every GitHub query and mutation to the resolved full owner/name repository
and PR number. Require every refreshed PR to retain that identity, and evaluate
checks, reviews, replies, resolutions, and merge eligibility only for its exact
current head SHA. Stop and restart the evaluation when the head changes.
Rebase or restack according to repository policy before trusting results. Review conflict resolutions and push safely. Preserve an explicit draft state unless the user asks to mark the PR ready.
Merge, deployment, and protection bypass each require explicit user authority. A request to finish review does not imply any of them.
2. Review Independently
Inspect the complete semantic diff against the correct base and fix confirmed defects. Run proportionate focused checks, then the repository's canonical CI-equivalent verification when practical. Treat generated artifacts by their canonical source and check the generated delta for drift.
3. Converge Reviews and CI
Run /rabbit-round for the current head. Push accepted fixes before replying to
review threads. Then refresh reviews and required checks for the new head.
When bots or CI are still running, use the environment's monitor or wait mechanism; do not occupy the shell with sleep polling. Repeat only when new evidence arrives: a completed check, new review, new commit, or changed thread state.
Investigate failures from their logs and fix causes within scope. Do not rerun a failed job repeatedly without a reason, weaken checks, reseed baselines, dismiss valid reviews, or bypass protections merely to make the PR green.
Never request an automated review (@coderabbitai review, @codex review, or a
timed re-request after a rate limit); reviews arrive on their own. Budget the loop:
at most two review rounds after the first green head. When actionable findings keep
arriving past that, keep the green head and triage the remaining findings yourself
with a concrete accept, push-back, or defer. Open one named follow-up PR for the
accepted fixes; make it stacked only when repository policy or the existing branch
stack requires that. Then reply to each deferred finding with that PR's URL, and
resolve the thread where the finding has one: the named follow-up is the
disposition, not a promise. A deferred top-level comment stays open; the reply is
its terminal state.
The budget never defers a release-blocking defect. A finding that names a security, authorization, data-loss, or data-corruption defect, and survives verification, is fixed on this head however late it arrives: shipping a known defect to keep a round count is the outcome the budget exists to avoid.
Show full SKILL.md (172 more words)Show less
4. Stop at a Real Terminal State
The latest pushed head has converged only when:
- required CI is green
- automated reviewers are terminal, not pending
- no actionable automated finding remains in a review thread or a top-level comment: each is implemented, already addressed, pushed back with evidence, or deferred to a named follow-up PR, and no verified release-blocking defect was deferred
- no unresolved human request for changes remains
- no blocking review or merge conflict remains
If convergence requires a user decision, new authority, unavailable credentials, or an external state change, report the exact blocker and the evidence already collected.
Merge only when explicitly requested. Use the repository's documented merge entry point (a merge script or queue) when one exists; a raw merge command bypasses its assertions. Never use admin authority to bypass a correctness failure. After any authorized merge, verify the PR state and report the resulting commit.
Report the PR URL, latest head, review and CI state, changes made, validation run, and whether the terminal state is ready, merged, or blocked.
© stella, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/finish-pr of stella/stella.
Open the folder on GitHubat commit b225fd8
Compare with similar skills
Finish PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Finish PR this skillstella/stella | 258 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Record PR Demo
payloadcms/payload
A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.
More from stella/stella
All 24 skills in this repoPlan
stella/stella
Create a concise, evidence-backed implementation plan in the repository planning area when the user explicitly asks for a plan.
Answer From Sources
stella/stella
Answers data-protection (GDPR) questions grounded in the regulation and supervisory guidance, with a citation for every claim.
Check Against Rules
stella/stella
Reviews a non-disclosure agreement against the firm's NDA checklist and reports findings with citations.
Intake To Draft
stella/stella
Collects the facts of an unpaid invoice, then drafts a payment demand letter.
Conventions Perf
stella/stella
Apply when a performance-guard check (network baseline, bundle baseline, DB query count, loader-prefetch lint, RC bailouts) fails or when touching a hot route/endpoint.
Conventions Use Effect
stella/stella
Apply when writing or reviewing React effects in apps/web. An agent skill from stella/stella.
Related
Categories
Questions about Finish PR
What does Finish PR do?
Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it. Finish PR is an agent skill from stella/stella. Drive an existing pull request to a converged review state by addressing feedback and CI repeatedly; merge only when the user explicitly requests it.
When should I use Finish PR?
Finish PR fits situations like: explicitly requests it; tasks that involve Pull requests.
How do I install Finish PR in Claude Code?
Run `npx skills add stella/stella --skill finish-pr -a claude-code`. Or copy the skill folder (.agents/skills/finish-pr in stella/stella) into .claude/skills/finish-pr in your project. Claude Code loads it when a task matches its description.
How do I install Finish PR in Codex?
Run `npx skills add stella/stella --skill finish-pr -a codex`. Or copy the skill folder (.agents/skills/finish-pr in stella/stella) into .agents/skills/finish-pr in your project. Codex loads it when a task matches its description.
Can I use Finish PR in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stella/stella --skill finish-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finish-pr, .gemini/skills/finish-pr, .github/skills/finish-pr and .opencode/skills/finish-pr in your project.
What does Finish PR need to run?
SKILL.md names no scripts, command-line tools or credentials: Finish PR is instructions for the agent only.
Does Finish PR access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Finish PR safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Finish PR use?
Finish PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Finish PR use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Finish PR?
Skills that share tags, products or a category with Finish PR: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finish PR?
stella (a GitHub organization) maintains it in stella/stella, which has 258 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 9, 2026.
Source: stella/stella on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.