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
- augments-labs/sdlc-skillstheir own version, first seen Aug 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- augments-labs/sdlc-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- skills/coding/redis-agent-skills/AGENTS.mdAGENTS.md
- skills/coding/redis-agent-skills/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- autopilotSkill
- book-studySkill
- brainstormingSkill
- browser-useSkill
- cavemanSkill
- androidSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-designSkill
- supabase-postgres-best-practicesSkill
- theme-factorySkill
- vercel-react-best-practicesSkill
- web-design-guidelinesSkill
- context7-aware-codingSkill
- document-intakeSkill
- explore-codebaseSkill
- find-skillsSkill
- ohc-coding-disciplineSkill
- pdfSkill
- ralphSkill
- requesting-code-reviewSkill
- retrospectiveSkill
- seo-auditSkill
- skill-creatorSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- writing-plansSkill
- writing-skillsSkill
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
- Distinctive: line 18
Must exit 0 before proceeding.
- Distinctive: line 21
Add to CHANGELOG.md under [Unreleased]:
- Distinctive: line 48
Run full test suite on branch tip.
≈ “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.
Files
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.shMust 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 updatedStep 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 -dOptional: Production readiness checklist
For production-grade merges, skim references/production-checklist.md and satisfy or explicitly defer items.
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
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.

