finishing-work
Skill0 starsChanged 46 days agoMITView on GitHub
Use when implementation is complete and verified, and the work needs to be integrated, handed off, or cleaned up
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bostonaholic/rpikittheir own version, first seen Nov 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
- bostonaholic/rpikit★ 19same 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 repository13 other files it gives its agents.
- debugging-systematicallySkill
- delegating-to-subagentsSkill
- executing-plansSkill
- investigating-in-parallelSkill
- isolating-workspacesSkill
- planning-workSkill
- receiving-reviewSkill
- requesting-reviewSkill
- shaping-designsSkill
- testing-firstSkill
- using-tackleSkill
- verifying-before-claimingSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- could be automatic: a setting could enforce it
- Distinctive: line 13
Work on a branch or in a worktree: follow the steps below.
- Distinctive: line 23
Keep the branch as it is for later
- Distinctive: line 26
Leave out options that don't fit.
- Distinctive: line 28
Merge: update the base branch, merge, and re-run the tests on the merged result before deleting the feature branch.
- Distinctive: line 34
Never force-push, rewrite shared history, or delete work without an explicit request.
≈ “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 Work
Close the loop: confirm the work holds up, tell the user what they're getting, and integrate it the way they want.
Scale it
- Trivial / Small, in place: a short summary of what changed and how it was verified. Done.
- Work on a branch or in a worktree: follow the steps below.
How
- Verify the whole change with the full test suite, plus build and lint if the project uses them. If something fails, report it and fix it before offering to integrate.
- Summarise: what was built, how it was verified, any deviations from the plan, and anything left unverified or deferred.
- Confirm the base branch the work split from (usually
mainormaster; ask if unsure). Offer the integration options that apply, with a recommendation:
- Merge into the base branch locally
- Push and open a pull request
- Keep the branch as it is for later
- Discard the work
Leave out options that don't fit. There's no PR without a remote, and no merge without git.
- Carry out the choice:
- Merge: update the base branch, merge, and re-run the tests on the merged result before deleting the feature branch.
- PR: push, then create the PR with a summary and a test plan. Follow the project's PR conventions.
- Keep: report the branch name and workspace path.
- Discard: list exactly what will be deleted (branch, commits, workspace) and get explicit confirmation first.
- Clean up worktrees or scratch copies once they're no longer needed. Keep them if the user may come back (Keep, or a PR under review).
Never force-push, rewrite shared history, or delete work without an explicit request.
Skip or shorten when
- The user has already said how to integrate. Do that.
- There's no git. Summarise, and point to any scratch copies.
Done means
The user knows what was delivered and how it was verified, the chosen integration is complete, and nothing is left dangling.
Next
None. The work is done.
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.