finish-branch
Skill1 starsChanged 5 months agoMITView on GitHub
Complete development work — verify tests, present merge/PR/discard options, clean up worktree and branch
- Commits and pushes
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Yesterday-AI/ytstacktheir own version, first seen Nov 8, 2026
- LARi-UQAC/ResearchToolstheir own version, first seen Nov 8, 2026
- sergvss/agents-best-teamstheir own version, first seen Nov 1, 2026
- slowernet/dietpowerstheir own version, first seen Oct 4, 2026
- Chrike/coding-agent-skillstheir own version, first seen Aug 4, 2026
- jnsfhrmnn/jf-agentic-coding-starter-kittheir own version, first seen Jul 18, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- LARi-UQAC/ResearchTools★ 14same name
- ariadoss/superskills★ 12same name
- KhaledSaeed18/dotclaude★ 5same name
- sergvss/agents-best-teams★ 2same name
- Yesterday-AI/ytstack★ 2same name
- Chrike/coding-agent-skills★ 1same name
- jnsfhrmnn/jf-agentic-coding-starter-kit★ 1same name
- slowernet/dietpowers★ 0same 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 repository84 other files it gives its agents.
- api-design-reviewerSkill
- api-test-suite-builderSkill
- ask-mattSkill
- aws-solution-architectSkill
- captureSkill
- changelog-generatorSkill
- ci-cd-pipeline-builderSkill
- cloud-securitySkill
- codebase-designSkill
- codebase-onboardingSkill
- code-reviewerSkill
- context-compressSkill
- context-modeSkill
- database-designerSkill
- database-schema-designerSkill
- dependency-auditorSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- env-secrets-managerSkill
- firecrawlSkill
- focused-fixSkill
- frontend-designSkill
- get-shit-doneSkill
- git-guardrails-claude-codeSkill
- git-worktree-managerSkill
- git-worktreesSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- incident-commanderSkill
- incident-responseSkill
- mcp-builderSkill
- memSkill
- migration-architectSkill
- monorepo-navigatorSkill
- observability-designerSkill
- performance-profilerSkill
- playwright-testingSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- prompt-engineeringSkill
- prototypeSkill
- pr-review-expertSkill
- rag-architectSkill
- red-teamSkill
- reflectSkill
- resolving-merge-conflictsSkill
- root-cause-tracingSkill
- runbook-generatorSkill
- self-evalSkill
- senior-architectSkill
- senior-backendSkill
- senior-devopsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Tests fail?: Stop. Fix before proceeding.
- Distinctive: line 75
Verify tests before presenting options
- Distinctive: line 77
Don't clean up worktree for Option 2 (PR needs it)
- Distinctive: line 78
Don't run git worktree remove from inside the worktree
- Very specific: line 79
Always cd to main repo root first
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Finish Branch
Guide completion of development work with structured options.
When to Use
- Implementation is complete
- All tests pass
- Ready to integrate or discard work
Process
Step 1: Verify Tests
npm test / cargo test / pytest / go test ./...Tests fail? Stop. Fix before proceeding.
Step 2: Detect Environment
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)Step 3: Present Options
Normal repo or named-branch worktree:
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work
Which option?Detached HEAD (3 options):
1. Push as new branch and create a Pull Request
2. Keep as-is (I'll handle it later)
3. Discard this workStep 4: Execute
| Option | Action |
| 1. Merge locally | Checkout base → pull → merge → verify tests → cleanup worktree → delete branch |
| 2. Create PR | Push branch (git push -u origin <branch>) — keep worktree alive for PR iteration |
| 3. Keep as-is | Report preserved state, no cleanup |
| 4. Discard | Confirm with typed "discard" → remove worktree → force-delete branch |
Step 5: Cleanup (Options 1 & 4 only)
# From main repo root
git worktree remove <worktree-path>
git worktree pruneRules
- Verify tests before presenting options
- Get typed confirmation for discard
- Don't clean up worktree for Option 2 (PR needs it)
- Don't run
git worktree removefrom inside the worktree - Always
cdto main repo root first
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.

