skills.rest
iadr-dev
iadr-devCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-branch

Enforce a pre-merge checklist for Git branches and generate changelog and PR descriptions.

2|Updated Apr 26, 2026
Search Tags:#test verification#pre-merge checklist#git worktree cleanup#changelog entry#pull request description#lint and typecheck
One-click install
npx skills add https://github.com/iadr-dev/colab --skill finishing-a-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-branch
Source: https://github.com/iadr-dev/colab/tree/main/skills/finishing-a-branch
Command: npx skills add https://github.com/iadr-dev/colab --skill finishing-a-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

finishing-a-branch ensures a branch is truly merge-ready by enforcing a pre-merge quality gate, producing consistent PR and changelog updates, and removing temporary worktrees and branches after shipping.

Core Features & Use Cases

  • Pre-merge quality enforcement: Verifies the branch has no debug code, runs the full test suite, and passes lint/type checks before merging.
  • Release documentation consistency: Generates a structured changelog entry and a PR description template aligned to the change you shipped.
  • Worktree hygiene: Cleans up OHC-related worktrees and branches to keep the workspace stable and reproducible.
  • Use case: You implement a feature or fix, mark it as ready to ship, and want a repeatable checklist that prevents silent test skips, forgotten debug statements, and inconsistent release notes.

Quick Start

Run finishing-a-branch to validate your branch, draft your changelog and PR description, and clean up worktrees after a successful merge.

Frequently Asked Questions about finishing-a-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a pre-merge checklist to prevent debug code and skipped tests from reaching main?▼

You can enforce a pre-merge checklist by running a deterministic script that scans for debug code, validates lint and typecheck passes, and ensures no tests are skipped before merging a branch to main.

How do I generate a consistent changelog entry and pull request description before merging?▼

Generating a consistent changelog entry and pull request description requires standardizing release documentation by producing structured content that aligns with the specific changes shipped on the branch.

What is the best way to automate git worktree cleanup after a successful branch merge?▼

Automating git worktree cleanup involves removing temporary worktrees and branches after shipping to keep the workspace stable and reproducible, preventing local repository clutter from accumulating.

Can I use a pre-merge quality gate for git branches using a ship keyword trigger?▼

Yes, you can apply a pre-merge quality gate to PR workflows by using a ship keyword or a specific trigger, which executes the validation script and standardizes release documentation before finalizing the merge.

How do I check my git branch for silent test skips before creating a pull request?▼

Checking for silent test skips involves executing a pre-merge verification script that runs the full test suite deterministically, failing the checklist if any tests are bypassed or skipped before pull request creation.

Related Skills

Explore More Software Engineering Skills→
corbat-techcorbat-tech
1

worktree-finish

Merges a verified Git worktree branch and cleans it up afterward.

Official
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
TbK0ngTbK0ng

finish-work

Enforce a pre-commit checklist with lint, typecheck, and tests.

Community
Intermediate
auldsyababuaauldsyababua
6

Update Linear Post-Job

Mark child Linear issues as Done and update parent work blocks.

Community
Intermediate