agentleFS
iadr-deviadr-dev/colab/skills/finishing-a-branch/SKILL.md

finishing-a-branch

Skill2 starsChanged 7 months agoMITView on GitHub

Pre-merge checklist, changelog entry, PR description, and worktree cleanup. Ensures no debug code, all tests pass, documentation updated. Triggers on keyword "ship" or when SHIP workflow is active.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Must exit 0 before proceeding.

    line 18
  2. Distinctive:

    Add to CHANGELOG.md under [Unreleased]:

    line 21
  3. Distinctive:

    Run full test suite on branch tip.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finishing a Branch

The final steps before merging. Never skip the pre-merge check.

Step 1: Pre-merge Check

bash skills/finishing-a-branch/scripts/pre-merge-check.sh

Must exit 0 before proceeding. Fix and re-run if it fails.

Step 2: Changelog Entry

Add to CHANGELOG.md under [Unreleased]:

### Added
- {feature}: {one-line description} — {PR link}
### Fixed
- {bug}: {what was wrong and what was fixed} — {PR link}

Step 3: PR Description

## What
{2-3 sentences: what this PR does, not how}

## Why
{1-2 sentences: why this change was needed}

## How to Test
1. {step-by-step test instructions}
Expected: {what success looks like}

## Checklist
- [ ] Tests pass
- [ ] No debug code left
- [ ] Changelog updated

Step 4: Final Test Run

Run full test suite on branch tip. Do not proceed if any test fails or skips.

Step 5: Clean up Worktrees

git worktree list | grep ohc/ | awk '{print $1}' | xargs -I{} git worktree remove {}
git branch | grep ohc/ | xargs git branch -d

Optional: Production readiness checklist

For production-grade merges, skim references/production-checklist.md and satisfy or explicitly defer items.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.