finish-work
Skill0 starsChanged 19 days agoMITView on GitHub
Use when a change is ready ("finish", "wrap up", "we're done", "open the PR"). Checks the docs moved with the change, runs the full gate with the plugin's types, tries in a real session what no test can reach, commits, opens a draft PR, reviews it with review-code until it is clean, and asks the maintainer to mark it ready or merge it; the maintainer squash-merges.
- Deletes or force-pushes
- Commits and pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lennoxsaint/Skillstheir own version, first seen Nov 15, 2026
- futex-ai/skillstheir own version, first seen Oct 25, 2026
- lxyer/multi-agent-collaboration-systemtheir own version, first seen Apr 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- lennoxsaint/Skills★ 48same name
- futex-ai/skills★ 1same name
- lxyer/multi-agent-collaboration-system★ 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- review-codeSkill
- review-planSkill
- start-workSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Docs in the same change: Check each thing that describes the change moved with it: README.md and plugin/README.md for what users see (a …
- Very specific: line 32
Open a draft PR: Write the body to .local/pr-body.md from .github/pull_request_template.md.
- Very specific: line 42
If main moved: git fetch origin, git rebase origin/main, git push --force-with-lease.
- Very specific: line 47
Clean up: after the merge: git switch main and git pull.
- Distinctive: line 60
Add AI co-author trailers, "Generated with" lines or session links: commits, PR titles, PR bodies.
“Common” is measured: kept by at least 6 in 10 of the 3 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 a change
Done means node tools/gate.ts full passed, REVIEW.md is answered and review-code is clean, not that the work
feels complete. main takes PRs only, and the maintainer squash-merges them (AGENTS.md, How a change lands).
Steps
- Docs in the same change. Check each thing that describes the change moved with it:
README.mdandplugin/README.mdfor what users see (a command, the option, what the plugin keeps),docs/design.mdfor how it works,CHANGELOG.mdunder Unreleased when users notice it,AGENTS.mdfor a changed path, command or rule, and the plan when the work departed from it (where and why). Write them the wayAGENTS.mdasks. - The plugin's types. For a change under
plugin/: isplugin/.claude-plugin/types/there, written by the Claude Code you run? If not, load the mod once (claude --plugin-dir plugin, then quit), so the gate checks the types instead of skipping them. CI can't. - The gate:
node tools/gate.ts full. Fix every failure; never weaken a test, a check or an ignore to pass. - Try it in a real session, for a change a test can't reach (a restore, the band, the pane, the process lookup,
a command line): with the installed copy turned off (
claude plugin disable session-restore@session-restore), startclaude --plugin-dir pluginin a folder, send a prompt, cut it off (close its terminal window), then open another session the same way and use the band or/restore. Note the Windows and Claude Code versions, what worked, and what you could not show (another shell, no Windows Terminal, macOS). Turn the installed copy back on. - Commit: a plain imperative subject that says what changed, a body that says why,
Refs #<n>. No tool attribution:commit-msgrefuses it. - Open a draft PR. Write the body to
.local/pr-body.mdfrom.github/pull_request_template.md. Push withgit push -u origin HEAD(pre-pushruns gate quick), thengh pr create --draft --title "<plain imperative sentence>" --body-file .local/pr-body.md. The title becomes the commit subject onmain. Say it's open and how to see it all: the PR's Files tab, orgit diff origin/main...HEAD. - Review with
review-codeuntil it isclean. Commit each round's fixes with gate quick passing, and the record indocs/reviews/. Put the verdict and the record's path in the body's Review section:gh pr edit <n> --body-file .local/pr-body.md. - CI on the head commit:
gh pr checks <n> --watch. A red check is fixed, never skipped. - Ask the maintainer, as one question with a recommendation: mark it ready (
gh pr ready <n>), merge it, or leave it a draft.- If
mainmoved:git fetch origin,git rebase origin/main,git push --force-with-lease. A rebase that changes code needs the gate again. - Merge only on the maintainer's word:
gh pr merge <n> --squash --delete-branch --subject "<title> (#<n>)" --body-file .local/squash.md, a body that says what and why and endsRefs #<issue>orCloses #<issue>. No HTML comments, no tool attribution.
- If
- Clean up after the merge:
git switch mainandgit pull; a worktree goes withgit worktree remove <path>from the main checkout. Work that turned up on the way becomes an issue (gh issue create).
Done means
gate fullpassed on the head commit with the plugin's types checked,review-codeis clean for exactly this code, and the PR says how what no test reaches was tried.- The PR is ready for the maintainer, merged on their word, or left a draft by their choice.
Never
- Open, mark ready or merge a PR with a failing gate or CI, or with a review of different code.
- Mark a
REVIEW.mdquestion yes without its evidence. - Add AI co-author trailers, "Generated with" lines or session links: commits, PR titles, PR bodies.
- Push to
main, merge without the maintainer's word, or push to someone else's branch. - Bump
plugin.json's version outside a release PR (docs/releasing.md).
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.

