Finishing A Development Branch

Finishing A Development Branch is a DevOps skill for Claude Code, published by GanyuanRan in Aegis.

1.1K stars50 forkson GanyuanRan/AegisAdded 2026/08/21+2% in starsRepository updated 2026/08/19

agent-skillsai-agentsai-codingarchitecture-driven-developmentawsome-coding-pluginbaseline-firstclaude-codecodexcoding-agentsdivedsh-pluginevidence-drivenfirst-principlesopencodesoftware-architecturespec-driven-developmentspec-kit

Install in seconds

Install Finishing A Development Branch

Copy Finishing A Development Branch into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/GanyuanRan/Aegis/tree/main/skills/finishing-a-development-branch ~/.claude/skills/finishing-a-development-branch

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/GanyuanRan/Aegis.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/finishing-a-development-branch/SKILL.md in GanyuanRan/Aegis
Installs to: ~/.claude/skills/finishing-a-development-branch
Collection: One of 22 skills cataloged from this repository
Category: DevOps — 798 skills

What Finishing A Development Branch does

Finishing A Development Branch handles verification, merge or PR decisions, and ownership-aware cleanup for a task-created Git branch or worktree. Use it when verified work needs integration or the user asks to manage branch lifecycle steps.

Finishing A Development Branch is cataloged under DevOps on DirSkills. Finishing A Development Branch comes from a repository tagged agent-skills, ai-agents, ai-coding, architecture-driven-development and awsome-coding-plugin.

Documentation

README

Excerpt

Finishing a Development Branch

Overview

Integration choice and checkout lifetime are separate. Verify first, mutate only task-owned resources, then prove what was removed or retained.

Core principle: fresh evidence -> authorized integration -> ownership-aware cleanup -> Git/path readback.

Announce at start: explain which branch/worktree lifecycle is being closed.

Step 1: Environment and Ownership Detection

Read the task's TaskStartSnapshot and current repository state. Record:

root, HEAD, branch/detached state, upstream divergence, and active Git ops;
staged/unstaged/untracked paths and the task-owned delta;
git worktree list --porcelain;
branch/worktree creator, task ownership, base branch, and cleanup trigger.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Finishing A Development Branch

What else does GanyuanRan publish alongside Finishing A Development Branch?
Finishing A Development Branch is one of 22 skills that DirSkills catalogs from GanyuanRan/Aegis, the repository it ships in. Its siblings there include Aegis Goal Framing, Anti-Entropy Governance and Brainstorming. Each one is a separate skill with its own page in this directory, installs the same way Finishing A Development Branch does, and is maintained by GanyuanRan in that same repository. The rest of the collection is listed on the GanyuanRan/Aegis page.
How does Finishing A Development Branch compare to other DevOps skills?
Finishing A Development Branch ranks #414 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Finishing A Development Branch against them. Open each page to compare what they document and how they install.