finishing-a-development-branch

Validate tests and guide merge or PR workflows for development branches.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/miguelarcjr/shark-ai --skill finishing-a-development-branch-miguelarcjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/miguelarcjr/shark-ai/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/miguelarcjr/shark-ai --skill finishing-a-development-branch-miguelarcjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to complete work on a development branch by validating tests, detecting repository state, and presenting deterministic options for merge, PR, or cleanup.

Core Features & Use Cases

  • Test guardrails: ensures tests pass before finishing.
  • Environment-aware options: adapts available actions based on repo state (normal, named worktree, detached HEAD).
  • Structured workflow execution: executes the chosen merge/PR/cleanup path and performs required cleanup steps.
  • Use Case: when a feature branch is ready for integration, this skill provides a safe, auditable path to finalization.

Quick Start

Verify tests pass, detect repository state, present four structured options, and execute the chosen path.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I safely merge a git feature branch only after tests pass?

To safely merge a git feature branch, you need a workflow that enforces test validation before integration. This skill automates that finalization by running test guardrails and blocking merges or pull requests until tests pass successfully.

Can I finalize a development branch from a detached HEAD or a named worktree?

Yes, you can finalize a development branch from a detached HEAD or a named worktree. The skill detects the repository state and adapts the available merge, pull request, and cleanup options to match the specific environment.

What is the best way to automate pull request creation and branch cleanup?

The best way to automate pull request creation and branch cleanup is using a structured workflow that presents deterministic options. This skill executes a defined sequence of actions, handling merge paths and required cleanup steps automatically.

Does this git workflow tool require any specific dependencies or components?

No, this git workflow tool does not require any specific dependencies or components. It operates independently to detect repository state, validate tests, and guide merge or pull request workflows without external integrations.

Why should I use a guided merge workflow instead of a standard git merge?

You should use a guided merge workflow instead of a standard git merge to ensure a safe, auditable path to finalization. It enforces test guardrails, detects repository state, and provides explicit deterministic options to prevent integration errors.