finish-dev

Verify tests and guide merge, PR, keep, or discard decisions for finished branches.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mengdehong/opencode-dotfiles --skill finish-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-dev
Source: https://github.com/mengdehong/opencode-dotfiles/tree/main/skills/finish-dev
Command: npx skills add https://github.com/mengdehong/opencode-dotfiles --skill finish-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams finalize finished development work by coordinating test verification and providing structured options to merge, open a PR, keep, or discard the branch, ensuring a clean handoff to deployment.

Core Features & Use Cases

  • Verify that all tests pass and code changes are stable before integration.
  • Determine a base branch and present exactly four options: merge locally, push and create a PR, keep the branch as-is, or discard the work.
  • Clean up worktrees and branches according to the chosen flow, with guardrails to prevent unsafe actions.

Quick Start

After implementing changes and passing tests, run the finish-dev workflow to choose between merging locally, pushing a PR, keeping the branch, or discarding it.

Frequently Asked Questions about finish-dev

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

FAQPage Schema
How do I finalize a git branch after all code changes pass tests?

Finalizing a finished dev branch involves verifying tests, determining the base branch, and choosing to merge locally, push a pull request, keep the branch, or discard it. This workflow automates that decision process with guardrails against unsafe actions.

What is the best way to guide a team through a merge or pull request decision?

The best way to guide merge or pull request decisions is presenting exactly four structured options after test verification: merge locally, push and create a PR, keep the branch as-is, or discard the work, ensuring a clean handoff to deployment.

Can I automate branch cleanup and worktree removal after merging?

Yes, you can automate branch cleanup and worktree removal after merging. The workflow cleans up worktrees and branches according to your chosen flow, with explicit confirmation guardrails to prevent unsafe actions during cleanup.

Does the finish-dev workflow require test verification before merging?

Yes, test verification is required before merging. The workflow enforces requirements for test verification and base-branch detection, preventing unsafe integration actions without explicit confirmation that all tests pass and code changes are stable.

What are the limitations of automating dev work finalization?

A limitation of automating dev work finalization is that it prevents unsafe actions without explicit confirmation. It requires tests to pass and base-branch detection to succeed before presenting merge, PR, keep, or discard options.

How do I discard local development work safely without breaking the base branch?

To discard local development work safely, the workflow offers a discard option among its four structured choices. It enforces test verification and base-branch detection, using guardrails to prevent unsafe actions and protect the base branch during cleanup.