skills.rest
Haemeok
HaemeokOFFICIAL
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify tests and finalize development branches with merge, PR, and cleanup options.

Updated Mar 13, 2025
Search Tags:#workflow#testing#development#merge#branch-management#pull-request#compounding
One-click install
npx skills add https://github.com/Haemeok/Capstone-frontend --skill finishing-a-development-branch-haemeok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Haemeok/Capstone-frontend/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Haemeok/Capstone-frontend --skill finishing-a-development-branch-haemeok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This override skill helps teams finalize development work by guiding the merge/PR/cleanup decisions, ensuring tests pass, and capturing session learnings via a mandatory compounding step.

Core Features & Use Cases

  • Clarifies when and how to merge or push a PR after development is complete.
  • Automates selection among structured options and ensures proper cleanup and documentation.
  • Captures and compounds lessons to persist insights for future sessions.

Quick Start

Review test results, select one of the four completion options, and let the system finalize the work while recording compounding lessons.

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 finalize a development branch after feature work is complete?▼

Finalizing a development branch involves verifying tests pass, resolving the base branch, choosing a merge or pull request option, executing the cleanup, and compounding session lessons.

What is the best workflow for merging a feature branch locally versus pushing a pull request?▼

The best workflow provides structured selection among four completion options: merging locally, pushing a pull request, keeping work, or discarding it, followed by automated worktree cleanup.

Why should I capture lessons after completing a development branch merge?▼

Capturing lessons after a branch merge is necessary because the workflow mandates a compounding step to persist insights and learnings for future development sessions.

Does branch finalization require tests to pass before pushing a pull request?▼

Yes, branch finalization requires test verification before guiding the pull request or merge selection to ensure the development work is stable.

When do I need to clean up worktrees during branch management?▼

Worktree cleanup is needed during branch management after finalizing your selected merge, pull request, or discard option to remove residual development artifacts.

Can I keep my local work instead of merging or pushing a development branch?▼

Yes, you can keep local work; the branch finalization workflow includes a structured option to retain work without merging or pushing a pull request.

Related Skills

Explore More Software Engineering Skills→
benjgradbenjgrad

finishing-a-development-branch

Verify tests pass, then merge locally, open a PR, keep, or discard a Git branch.

Community
Advanced
notquenotque
415

feature-release

Merge validated feature branches into main via pull requests with optional release tagging.

Community
Intermediate
xlelibertyxleliberty

finishing-a-development-branch

Verify tests and merge or create pull requests for development branches.

Community
Advanced
Michae2xlMichae2xl

finishing-a-development-branch

Automate merge, cleanup, and test verification for development branches.

Community
Intermediate