finish
Skill0 starsChanged 45 days agoMITView on GitHub
Integrate finished work: verify it, then merge locally, push and open a pull request, or keep the branch — and clean up the worktree safely. Use when implementation is done and the branch needs to go somewhere, when the user says "wrap it up", "merge it", "open a PR", or at the end of spec-run.
- 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 7 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
- AnthropicSkill
start
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
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 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 repository14 other files it gives its agents.
- architectureSkill
- debugSkill
- fan-outSkill
- merge-conflictsSkill
- reviewSkill
- spec-adoptSkill
- spec-amendSkill
- spec-boundariesSkill
- spec-implementSkill
- spec-initSkill
- spec-reviewSkill
- spec-runSkill
- spec-shapeSkill
- tddSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Verify, choose, integrate, clean up.
- Distinctive: line 19
Capture where you are: before changing directory: the branch, the base branch (confirm it if unsure), the worktree path (git rev-parse …
- Distinctive: line 27
Keep the branch as it is.
- Very specific: line 47
Clean up: only what this workflow created: a worktree under .worktrees/ or one the harness's worktree tool made.
- Very specific: line 55
No force-push, no reset --hard on a shared branch, no branch -D.
“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
Verify, choose, integrate, clean up.
Procedure
- Verify. The full suite, typecheck, lint, and — with a spec layer —
node specs/registry.mjs check, all with output from this turn. Red stops here: integration waits for green, and the failure is reported. - Capture where you are before changing directory: the branch, the
base branch (confirm it if unsure), the worktree path
(
git rev-parse --show-toplevel), and the main checkout (git rev-parse --git-common-dir). Choose — or use the choice spec-run's readiness step recorded:
- Merge into the base branch locally.
- Push and open a pull request.
- Keep the branch as it is.
Pushing and opening a PR act outside the repository: they need the user's yes, given now or at spec-run's readiness step. Discarding work happens only when the user asks for it by name, and after they confirm the exact branch.
- Integrate.
- Merge: from the main checkout, update the base branch, then
git merge --no-ff --no-commit <branch>and run the suite on the merged tree before committing. Green → commit the merge and clean up. Red →git merge --abort, keep the work branch, and report; nothing on the base branch changed. - Pull request: push the branch and open the PR (
gh pr create). The body comes from the plan, not from reading the diff: what changed and why, the statement IDs now true and the tests proving them, the verification commands and their results, rulings made during the run, and anything parked. Keep the worktree until the PR merges. - Keep: report the branch and worktree path.
- Merge: from the main checkout, update the base branch, then
- Clean up only what this workflow created: a worktree under
.worktrees/or one the harness's worktree tool made. Remove it withgit worktree remove. If git refuses because of untracked or modified files, show them and ask — never force it. Delete the merged branch withgit branch -d, which refuses unmerged work.
Rules
- No force-push, no
reset --hardon a shared branch, nobranch -D. - A rejected push is information: fetch, integrate, re-verify, push again.
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.