finish

Merge approved pull requests, close plans, and route homolog-to-main decisions.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill finish-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/finish
Command: npx skills add https://github.com/bravros/bravros --skill finish-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Completing a feature involves more than clicking merge: CI must be verified, the plan recorded as complete, local branches synced, and the homolog-to-main production decision routed to the operator. This Skill automates that entire landing sequence with strict safety gates so merges never happen against failing checks or stale approvals. ## Core Features & Use Cases - Gated PR Merge: Watches CI checks, enforces a CLEAN mergeStateStatus readiness gate, acquires a merge lock, and verifies post-merge blob hashes so no change is silently lost. - Plan Closure: Appends a completed event to .planning/events.jsonl for the plan and its backlog items linked to the merged PR. - Homolog-to-Main Routing: Reports the accumulated commit scope and asks the operator whether to merge homolog into main through its own PR gate, defer, or hand off the PR URL. - Use Case: After a feature PR is approved, invoke the Skill to watch CI, merge into homolog, fast-forward local branches, sweep stale review stamps, and decide whether production gets the accumulated work — ending with an explicit main @ <sha> status line. ## Quick Start Ask the agent to finish the feature by merging the approved PR and routing the main-merge decision.

Frequently Asked Questions about finish

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

FAQPage Schema
How do I safely merge an approved GitHub PR from the command line?▼

Run gh pr checks with --watch redirected to a file and capture the exit code, then verify mergeStateStatus is CLEAN before running gh pr merge with a literal PR number. This Skill automates that sequence including lock acquisition and post-merge verification.

How to merge a staging branch into main through a pull request?▼

Open a PR from homolog to main, wait for its full check suite and a CLEAN mergeStateStatus, then merge it. The Skill routes this as an operator decision with options to merge now, open the PR for manual merge, or accumulate.

Why does gh pr checks report success when a build failed?▼

Piping the command through tail replaces the exit code with the pipe's status, so a red build reads as rc=0. Redirect output to a file, capture RC=$? separately, then inspect the file.

What does mergeStateStatus UNSTABLE mean on a GitHub PR?▼

UNSTABLE means the PR is mergeable but a check is still pending or a non-required check failed. Green checks alone do not prove mergeability, so the Skill re-enters the CI watch and never merges through UNSTABLE silently.

Can this Skill push directly to the main branch?▼

No. Main is reached only by merging a PR, and the main-merge decision always belongs to the operator via an explicit prompt or a --merge-main/--no-main flag handed off from a calling skill.