ZES-finishing-a-development-branch

Verify tests and manage branch integration in Git repositories.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-finishing-a-development-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ZES-finishing-a-development-branch
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-finishing-a-development-branch
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-finishing-a-development-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent development workflows by enforcing a structured, test-verified process for merging, pushing, or discarding feature branches.

Core Features & Use Cases

  • Automated Verification: Ensures all tests pass before allowing any integration steps.
  • Environment Awareness: Detects whether you are in a standard repository or a detached HEAD worktree to provide appropriate options.
  • Safe Cleanup: Handles worktree removal and branch deletion only when safe, preventing accidental data loss or orphaned worktrees.

Quick Start

Invoke the finishing-a-development-branch skill to verify your current test suite and present the appropriate integration options for your branch.

Frequently Asked Questions about ZES-finishing-a-development-branch

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

FAQPage Schema
How do I enforce test verification before merging a Git development branch?

Git worktree cleanup during branch completion is managed by detecting detached HEAD states and providing environment-aware options. Safe cleanup handles worktree removal and branch deletion only when safe, which prevents accidental data loss or orphaned worktrees.

What is the best way to standardize Git workflow branch completion?

The best way to standardize Git workflow branch completion is to enforce a structured process for merging, pushing, or discarding feature branches. This eliminates inconsistent development workflows by requiring automated verification and explicit confirmation before modifying branch states.

How do I create a pull request and clean up a feature branch safely?

Yes, this branch finishing process works with Git worktrees by detecting whether you are in a standard repository or a detached HEAD worktree. This environment awareness allows it to provide appropriate integration and safe cleanup options for your specific setup.

Why does my development branch integration fail without passing tests?

Your development branch integration fails without passing tests because the workflow enforces automated verification to ensure code integrity. It requires successful test execution before allowing any integration steps to prevent merging broken code.