finish-work

Enforce pre-merge gates and CI checks before finalizing a development branch.

3|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/nuttaruj/rolepod --skill finish-work-nuttaruj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-work
Source: https://github.com/nuttaruj/rolepod/tree/main/core/skills/finish-work
Command: npx skills add https://github.com/nuttaruj/rolepod --skill finish-work-nuttaruj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you close out a development branch safely and deliberately by enforcing pre-merge gates, CI discipline, explicit authorization, and a clear decision about whether to merge, open a PR, keep working, or discard the branch.

Core Features & Use Cases

  • Pre-merge decision framework: Runs simplicity, test, failure-mode, and review checks before any ship action.
  • Safe branch outcomes: Guides the final choice among merge to main, open PR, keep open, or discard, with special handling for detached HEAD and worktrees.
  • Release readiness support: Adds launch checklist coverage for rollback, monitoring, on-call, feature flags, and migration safety when production traffic is involved.
  • Use Case: After implementation, verification, and review are complete, use this Skill to evaluate CI status, present the finish menu, prepare a PR body if needed, or coordinate a production-safe merge path.

Quick Start

Ask the AI to run the finish-work skill for your current branch and present the finish menu with gate status, CI results, recommendation, and the single action awaiting your authorization.

Frequently Asked Questions about finish-work

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

FAQPage Schema
How do I enforce pre-merge gates before merging a git branch to main?

Pre-merge gates evaluate simplicity, tests, failure modes, and reviewer status before finalizing a git branch. This gate validation ensures CI lanes pass and prevents incomplete code from merging to main.

What is the best way to triage red required CI lanes before opening a pull request?

The best way to triage red required CI lanes is running a dedicated CI triage check before finalizing your branch. This identifies failing required lanes so you can resolve issues before opening a pull request.

How do I safely clean up git worktrees when discarding an experiment branch?

To safely clean up worktrees when discarding an experiment, apply worktree-aware cleanup rules during the branch finalization process. This ensures detached HEAD states and worktrees are handled without losing uncommitted changes.

Can I coordinate a production launch with rollback and monitoring checks from a single branch workflow?

Yes, you can coordinate a production launch using release readiness support within a branch workflow. It adds launch checklist coverage for rollback, monitoring, on-call, feature flags, and migration safety before staging a production merge.

Does branch finalization support keeping work in progress instead of forcing an immediate merge?

Yes, branch finalization supports keeping work in progress. The finish menu presents multiple branch outcomes including merge to main, open PR, keep open, or discard, allowing you to delay merging until implementation is fully verified.