skills.rest
6BNBN
6BNBNCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify tests and present merge, PR, keep, or discard options for development branches.

134|12|Updated Feb 20, 2026
Search Tags:#git#workflow#testing#pull request#branching#code integration
One-click install
npx skills add https://github.com/6BNBN/FlowPilot --skill finishing-a-development-branch-6bnbn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/6BNBN/FlowPilot/tree/main/%E5%85%BC%E5%AE%B9codex%40cursor%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/codex%E4%B8%80%E9%94%AE%E5%AE%89%E8%A3%85%E6%8A%80%E8%83%BD/.codex-home-claude-parity/skills/finishing-a-development-branch
Command: npx skills add https://github.com/6BNBN/FlowPilot --skill finishing-a-development-branch-6bnbn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of finalizing development work by providing clear, safe, and structured options for integrating completed code, preventing common mistakes like merging broken code or losing work.

Core Features & Use Cases

  • Test Verification: Ensures all tests pass before proceeding.
  • Branch Integration Options: Offers choices for merging locally, creating a Pull Request, keeping the branch, or discarding the work.
  • Worktree Management: Safely cleans up or preserves worktrees based on the chosen action.
  • Use Case: After finishing a feature, use this Skill to automatically run tests, present options to merge into main or create a PR, and clean up your workspace.

Quick Start

Use the finishing-a-development-branch skill to finalize the current development branch.

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 development branch without breaking the main branch?▼

Safely merging a git development branch requires verifying all tests pass before offering structured integration options like merging locally or submitting a pull request, preventing broken code from entering the main branch.

What is the best way to clean up a git worktree after finishing a feature?▼

Cleaning up a git worktree after finishing a feature involves selecting an integration action like merging or discarding, which automatically manages workspace preservation or cleanup to prevent accidental data loss.

Can I create a pull request directly after verifying my branch tests pass?▼

Yes, creating a pull request is a structured integration option presented after verifying all branch tests pass, allowing direct code integration workflow transitions without manual steps.

Does this workflow support discarding incomplete git branch changes safely?▼

Yes, discarding incomplete git branch changes is supported through a dedicated discard option that manages worktree cleanup, addressing the risk of accidental data loss during code integration workflows.

Why should I use a structured process for code integration instead of merging directly?▼

Using a structured process for code integration prevents merging broken code, avoids accidental data loss, and eliminates ambiguous next steps by enforcing test verification and managing worktree cleanup before finalizing branches.

Related Skills

Explore More Software Engineering Skills→
HenquewlHenquewl
7

finishing-a-development-branch

Verify test suites and finalize git development branches through merge or cleanup.

Community
Advanced
zhaow-dezhaow-de

merge-pr

Merge reviewed GitHub pull requests with a merge commit.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
ESO-ToolkitESO-Toolkit
2

rebase

Automate rebasing stacked Git branches after a squash merge.

Official
Advanced