skills.rest
ccakmak60
ccakmak60COMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Present merge options after verifying tests and determining the base branch.

1|Updated Apr 17, 2026
Search Tags:#git#workflow#merge#pull-request#tests#finish#development-branch
One-click install
npx skills add https://github.com/ccakmak60/agentforge --skill finishing-a-development-branch-ccakmak60
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/ccakmak60/agentforge/tree/main/.trae/skills/finishing-a-development-branch
Command: npx skills add https://github.com/ccakmak60/agentforge --skill finishing-a-development-branch-ccakmak60

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch with a clean, deterministic path to integration by presenting predefined merge, PR, or cleanup options after verifying that tests pass.

Core Features & Use Cases

  • Structured decision workflow: Verifies tests, determines base branch, presents four options, and handles chosen workflow.
  • Guardrails and cleanup: Ensures post-merge cleanup and optional worktree management.
  • Use Case: When a feature branch is ready for integration, this skill guides next steps to minimize risk and time-to-merge.

Quick Start

Run the finishing-a-development-branch process on your feature branch to determine the next steps 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 finish a git development branch and ensure tests pass before merging?▼

To finish a development branch, the workflow verifies your tests pass, detects the base branch automatically, and then presents clear integration options to execute your chosen merge or pull request path.

What is the best way to handle git merge options when a feature branch is ready for integration?▼

Handling git merge options is structured through a four-option decision workflow that determines your base branch, verifies tests, and guides your pull request or direct merge execution to minimize integration risk.

How does base-branch detection work when completing a feature branch workflow?▼

Base-branch detection works by automatically identifying the correct integration target for your feature branch, ensuring that your tests are verified against the appropriate base before presenting merge or cleanup options.

Can I use a structured workflow to clean up git worktrees after a branch merge?▼

Yes, you can use this workflow to clean up worktrees after a branch merge, as it includes built-in guardrails for post-merge cleanup and optional worktree management following your chosen integration path.

What should I do if my feature branch tests fail during the merge process?▼

If your feature branch tests fail during the merge process, the workflow halts the integration steps, preventing the presentation of merge options until test verification succeeds and your codebase is stable.

Do I need to manually create a pull request when finishing a development branch?▼

No, you do not need to manually create a pull request, because the workflow presents a structured set of four integration options that handle PR generation and other git workflows automatically upon test success.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
ReinaMacCredyReinaMacCredy
223

finishing-a-development-branch

Verify tests and present merge, PR, or cleanup options for a development branch.

Community
Advanced
CarlosQ96CarlosQ96

smoke-check

Run smoke tests and generate PASS/FAIL reports for QA hand-off.

Community
Intermediate
sandgardenhqsandgardenhq
130

finishing-a-development-branch

Run tests before offering merge, pull request, or cleanup actions.

Official
Intermediate