Wrap up
Close a task: list the changes, fix stale docs, run checks, draft the commit.
$ npx skills add tonygorb/skills --skill wrap-upPick your agents from a list.
$ npx skills add tonygorb/skills --skill wrap-up -g -a claude-code -yInstalls into ~/.claude/skills/.
Open CustomizeSkills and upload it.
$ npx skills add tonygorb/skills --skill wrap-up -g -a codex -yInstalls into ~/.agents/skills/.
$ npx skills add tonygorb/skills --skill wrap-up -g -a cursor -yInstalls into ~/.agents/skills/.
$ npx skills add tonygorb/skills --skill wrap-up -g -a github-copilot -yInstalls into ~/.agents/skills/.
$ npx skills add tonygorb/skills --skill wrap-up -g -a gemini-cli -yInstalls into ~/.agents/skills/.
$ npx skills add tonygorb/skills --skill wrap-up -g -a opencode -yInstalls into ~/.agents/skills/.
$ npx skills add tonygorb/skills --skill wrap-up -g -a windsurf -yInstalls into ~/.codeium/windsurf/skills/.
Your agent uses it when you say
- “wrap up”
- “ready to commit”
What it does
The end-of-task pass: changes, docs, build, tests, a drafted commit. Never commits.
How it works
- 1Inventory the changes
- 2Check the scope
- 3Refresh the docs the diff made stale
- 4Build and typecheck
- 5Tests, once
- 6Draft the commit
- 7Never commit
Wrap up
The end-of-task pass: changes, docs, build, tests, a drafted commit. Never commits.
Steps
1. Inventory the changes
Run git status and git diff --stat HEAD (in a repo with no commits yet, git status alone).
List new, modified and deleted files.
Nothing changed: stop and say "nothing to wrap up".
2. Check the scope
If the diff spans unrelated projects or packages, stop and suggest wrapping up each one separately.
3. Refresh the docs the diff made stale
For each changed source file, search the docs folder for its path and the names it exports. Where a doc still describes the old path, name or behaviour, re-read the code and fix the doc. Keep a list of the docs you touched.
4. Build and typecheck
Run the project's build and typecheck scripts. On failure, show the errors and stop: no commit message for a broken build.
5. Tests, once
Run the unit tests in single-run mode (no watch). Skip slow end-to-end suites; mention them instead.
6. Draft the commit
Pick a Conventional Commit type (feat, fix, perf, refactor, docs, test, chore…), an
optional lowercase scope, and an imperative subject without a full stop. Then print exactly:
Changed files:
<list>
Docs refreshed:
<list or "none">
Build: PASS/FAIL
Typecheck: PASS/FAIL
Tests: PASS/FAIL/SKIPPED
Suggested commit:
<type>(<scope>): <subject>7. Never commit
Don't run git add, git commit or git push. The user reviews the draft and commits.