finisher

Commit pending changes, push to the PR branch, wait for CI, and merge the pull request.

12|2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/alexandrbasis/claudops --skill finisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finisher
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/finisher
Command: npx skills add https://github.com/alexandrbasis/claudops --skill finisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close out work by committing local changes, pushing, waiting for CI to green, and merging the PR. This universal skill works on any branch with an open PR; it gracefully handles tasks but does not require them.

Core Features & Use Cases

  • Commit and push local changes on a PR branch, wait for green CI, and merge the PR.
  • Supports base-case ships and phase-aware handoffs when tasks are split into phases.
  • Provides safeguards against merging when CI is not green or PR is closed.

Quick Start

Run the finisher after CI is green to merge the PR and close the work.

Frequently Asked Questions about finisher

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

FAQPage Schema
How do I automate committing, pushing, and merging a pull request after CI passes?

Automating the pull request merge workflow involves committing local changes, pushing to the PR branch, waiting for CI to pass, and merging. This requires an open PR and green CI status to execute successfully.

What is the safest way to wait for CI to pass before merging a git pull request?

The safest approach to wait for CI before merging a pull request uses automated safeguards that prevent merging when CI is not green or the PR is closed. It orchestrates git and GitHub CLI commands to verify status before completing the merge.

Can I use a merge automation workflow for multi-phase task handoffs?

Yes, you can use merge automation for multi-phase task handoffs. The workflow supports both single-task ships and phase-aware handoffs when tasks are split into phases, optionally updating phase handoffs during the merge process.

Does the automated PR merge workflow require specific git tools or environments?

The automated PR merge workflow requires an open pull request and green CI. It uses git and GitHub CLI commands to orchestrate the process, so both must be available in your environment to commit, push, and merge.

Why would a pull request fail to merge automatically when CI is red?

A pull request fails to merge automatically when CI is red because built-in safeguards prevent merging unless CI is green. This ensures broken code is not merged and requires the CI checks to pass before the merge proceeds.