skills.rest
CagesThrottleUs
CagesThrottleUsCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Guides branch completion through wiki sync, test verification, review gates, and merge or PR options.

Updated May 21, 2026
Search Tags:#git#code review#pull request#worktree#merge#branch cleanup#pre-merge checklist
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill finishing-a-development-branch-cagesthrottleus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill finishing-a-development-branch-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation is done, developers often skip documentation updates, merge with failing tests, or clean up worktrees incorrectly. This Skill enforces a structured completion checklist so every branch ships with synced docs, passing tests, and a passed review gate before integration. ## Core Features & Use Cases - Wiki and docs sync check: Verifies wiki entries, CLAUDE.md, and AGENTS.md reflect the branch's changes before any merge decision. - Test and artifact verification: Runs the test suite and checks for load tests, E2E tests, deployment artifacts, and DAST scans when required by the change type. - Review gate: Dispatches parallel reviewer agents (PR, spec, test-quality, security, plus artifact-specific reviewers) and blocks merge on Critical findings. - Structured integration options: Presents merge-locally, create-PR, or keep-as-is choices, with safe worktree cleanup and branch deletion ordering. - Use Case: After finishing a feature branch in a git worktree, invoke the skill to confirm docs are updated, tests pass, reviewers approve, then merge to main and clean up the worktree in the correct order. ## Quick Start Ask the AI to finish the current development branch using the finishing-a-development-branch skill and present the integration options.

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 feature branch after implementation is complete?▼

Verify tests pass on the final tree, run the review gate, then checkout the base branch, pull, merge, and re-run tests on the merged result. Only after a successful merge should you remove the worktree and delete the branch.

What should I check before creating a pull request?▼

Confirm documentation is synced with the branch changes, all tests pass, required artifacts like E2E tests and deployment runbooks exist, and reviewer agents report no Critical findings. Then push and create the PR as draft or ready based on review results.

Why does git branch -d fail when a worktree still exists?▼

Git refuses to delete a branch that is checked out in a worktree. Merge first, remove the worktree with git worktree remove from the main repo root, then delete the branch.

Can the review gate be skipped before merging?▼

The gate can be skipped only if the user explicitly requests it or the branch is a pure chore commit with no source file changes. Verify chore-only status by checking the diff contains no files outside config, lockfile, and documentation extensions.

When should documentation be updated relative to code changes?▼

Documentation must ship in the same branch as the behavior change, before merging. Wiki entries, CLAUDE.md, and AGENTS.md updates are committed alongside the code, not deferred to a later documentation pass.

Related Skills

Explore More Software Engineering Skills→
govctl-orggovctl-org
239

gov

Execute governed implementation workflows with govctl CLI for work items, RFC/ADR checks, phase gates, testing, and closure.

Official
Advanced
real-casereal-case

task-deliver

Commits verified changes and opens a pull request after a tool-backed verification gate passes.

Community
Advanced
wesleyosantos91wesleyosantos91
6

pre-pr

Analyze git diffs and run targeted review checklists to produce a GO/NO-GO report.

Community
Intermediate
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced