finish
Skill2 starsChanged 9 months agoMITView on GitHub
Use when feature implementation is complete and the branch is ready for final validation, PR creation, or merge.
- Commits and pushes
22 other projects use a version of this.
Adopted by
Most recently taken up by
- MarvinJWendt/skillstheir own version, first seen Nov 8, 2026
- leinardi/adversarial-review-looptheir own version, first seen Nov 8, 2026
- MammadovEshgin/clean-code-skilltheir own version, first seen Nov 8, 2026
- hex/claude-sessionstheir own version, first seen Nov 3, 2026
- CG-5228/ClaudeCodeImpactLab_hackathontheir own version, first seen Nov 1, 2026
- danielcherubini/skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use status, bootstrap and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 5 projects that use this
OpenAISkillbootstrap
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.
Also in 3 projects that use this
AnthropicSkillstart
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
Also in 3 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 6 projects that use this
dillonluiSkilldesign-review
Review a view or flow for UX and UI issues. Provides severity-ranked, actionable findings grounded in established design heuristics. Use when the user asks for design feedback, UX review, or UI critique.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 8 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- hacan359/tonkatsu_box★ 597same name
- alexeykrol/claude-code-starter★ 194same name
- hex/claude-sessions★ 54same name
- rlajous/claude-code-commands★ 30same name
- alexiolan/craft-skills★ 17same name
- danielcherubini/skills★ 14same name
- keefar/ticket-flow★ 4same name
- mmjclayton/agent-sop★ 4same name
- andreasbaumgartner/gilo★ 2same name
- clearsmog/claude-skills★ 2same name
12 more not listed
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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- checkpointSkill
- codereviewSkill
- commitSkill
- debugSkill
- estimateSkill
- healthSkill
- learnSkill
- lintSkill
- migrate-architectureSkill
- migrate-frameworkSkill
- onboardSkill
- planSkill
- recallSkill
- rememberSkill
- tddSkill
- tutorialSkill
- verifySkill
- worktreeSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
2
Distinctive
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 217
Never skip validation: - All checks must pass
- Distinctive: line 219
Offer cleanup: - Keep repo clean
“Common” is measured: kept by at least 6 in 10 of the 18 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 - Finalize Branch
Complete development branch with final validation and metrics.
Branch: $ARGUMENTS (or current branch)
Workflow
Step 1: Pre-Flight Checks
# Check current branch
git branch --show-current
# Check for uncommitted changes
git status
# Check for untracked files
git status --porcelainRequired:
- All changes committed
- No untracked files (or intentionally ignored)
- Not on main/master branch
Step 2: Run Full Validation
# TypeScript check
npx tsc --noEmit
# Lint
npm run lint
# Tests
npm test
# Build (if applicable)
npm run buildOutput:
──── Validation ────
TypeScript: PASS ✓
Lint: PASS ✓
Tests: PASS ✓ (42/42)
Build: PASS ✓Step 3: Generate Diff Summary
# Files changed
git diff main --stat
# Commits in branch
git log main..HEAD --onelineOutput:
──── Changes ────
Files changed: 12
Insertions: +450
Deletions: -120
Commits:
abc1234 feat: add user service
def5678 feat: add user component
ghi9012 test: add user tests
jkl3456 refactor: clean up typesStep 4: Session Metrics
──── Session Metrics ────
Branch: feature/user-profile
Duration: ~45 minutes
Commits: 4
Files:
Created: 5
Modified: 7
Deleted: 0
Code:
Lines added: 450
Lines removed: 120
Net change: +330
Tests:
Added: 8
Total passing: 42/42
Coverage: 87%
Agents used:
@planner: 1 invocation
@builder: 3 invocations
@reviewer: 1 invocation
Estimated tokens: ~18,500
Estimated cost: ~$0.28Step 5: Cleanup Checkpoints
# List checkpoints
git tag -l "checkpoint/*"
# Offer to clean
"Clean up checkpoint tags? (y/n)"If yes:
git tag -l "checkpoint/*" | xargs -n 1 git tag -dStep 6: Prepare for Merge
──── Ready for Merge ────
Branch: feature/user-profile
Base: main
Status: Ready ✓
Pre-merge checklist:
- [x] All tests passing
- [x] No TypeScript errors
- [x] Code reviewed
- [x] Checkpoints cleaned
Next steps:
1. Push: git push -u origin feature/user-profile
2. Create PR: gh pr create
3. Merge: After approvalOutput
──── /finish ────
Branch: [branch-name]
Validation:
TypeScript: PASS ✓
Lint: PASS ✓
Tests: PASS ✓ (N/N)
Build: PASS ✓
Changes:
Files: N changed
Lines: +N / -N
Commits: N
Metrics:
Tokens: ~N
Cost: ~$X.XX
Agents: N used
Checkpoints: [cleaned/kept]
Status: READY FOR MERGE ✓
Commands:
git push -u origin [branch]
gh pr create --title "[title]" --body "[body]"Validation Failures
If validation fails:
──── /finish ────
Branch: feature/user-profile
Validation:
TypeScript: FAIL ✗
Error: src/user.ts:42 - Property 'name' is missing
Lint: PASS ✓
Tests: FAIL ✗
2 tests failing
Status: NOT READY ✗
To fix:
1. Resolve TypeScript errors
2. Fix failing tests
3. Run /finish againAnti-Rationalization
| Excuse | Reality |
| "Tests pass locally, good enough" | CI runs in a clean environment. Your local cache hides broken imports and missing deps. |
| "I'll fix the lint errors in the next PR" | Technical debt compounds. Fix now or carry it forever. |
| "The build takes too long to run" | A broken build in production takes even longer to fix. Run it. |
| "I already reviewed the code mentally" | Mental review misses what automated checks catch. Run the full suite. |
Rules
- Never skip validation - All checks must pass
- Always show metrics - Transparency in cost
- Offer cleanup - Keep repo clean
- Don't auto-merge - Human decision
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.

