wrapup
Skill67 starsChanged 4 months agoMITView on GitHub
End-of-session closer. Compiles session notes, gets fresh-context review, updates COMP files, checks skill health and execution gaps, runs bloat check.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- ryanportfolio/HarnessFirmware.comtheir own version, first seen Nov 8, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- ryanportfolio/Harness-Firmwaretheir own version, first seen Nov 7, 2026
- ryanportfolio/Corewise.Academytheir own version, first seen Nov 1, 2026
- zommuter/dotclaude-skillstheir own version, first seen Nov 1, 2026
- atelier-fashion/adlc-toolkittheir own version, first seen Oct 31, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 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.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
- ryanportfolioSkill
apply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- atelier-fashion/adlc-toolkit★ 173same name
- sunitghub/canon-skills★ 9same name
- ebaumel/claude-wrapup★ 4same name
- maxekman/skills★ 4same name
- zommuter/dotclaude-skills★ 4same name
- PatriotAgenticLLC/better_claude_skillz★ 3same name
- iXanadu/tiding★ 2same name
- olzn/skills★ 2same name
- ryanportfolio/winuse-mcp★ 2same name
- Yesterday-AI/skills★ 2same name
15 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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autoresearchSkill
- brainstormSkill
- bug-huntSkill
- check-resolvableSkill
- compSkill
- debugSkill
- dialectic-reviewSkill
- distillSkill
- finalizeSkill
- implementSkill
- learnSkill
- plan-taskSkill
- premortemSkill
- red-teamSkill
- researchSkill
- retroSkill
- reviewSkill
- rsbSkill
- sessionsSkill
- shipSkill
- socratesSkill
- tradeoffSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
0
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 28
Read ~/.claude/skills/wrapup/session-notes-template.md — fill in each field from the session.
- Very specific: line 34
Read ~/.claude/skills/wrapup/comp-update-guide.md for what to update in each file.
- Very specific: line 37
Read ~/.claude/skills/wrapup/health-check-guide.md for the skill iteration check, execution reliability self-check, and cross-project …
- Very specific: line 43
Read ~/.claude/skills/wrapup/summary-template.md for the output format.
“Common” is measured: kept by at least 6 in 10 of the 23 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
/wrapup — Session Closer
End a working session cleanly.
Input
$ARGUMENTS
Flags
| Flag | Default | Purpose |
project:path | Current directory | Which project to finalize |
noprune | Off | Skip the bloat check |
prune | Off | Run full /prune instead of dryrun |
noreview | Off | Skip the session reviewer agent |
Process
Step 1: Compile Session Notes
Read ~/.claude/skills/wrapup/session-notes-template.md — fill in each field from the session.
Step 2: Session Review (fresh context)
Unless noreview flag is set. Read ~/.claude/skills/wrapup/session-review-guide.md for how to dispatch and present the reviewer.
Step 3: Update COMP Files
Read ~/.claude/skills/wrapup/comp-update-guide.md for what to update in each file.
Step 4: Skill & Execution Health
Read ~/.claude/skills/wrapup/health-check-guide.md for the skill iteration check, execution reliability self-check, and cross-project transfer.
Step 5: Bloat Check
Unless noprune flag is set, run the lightweight check described in ~/.claude/skills/wrapup/bloat-check-guide.md.
Step 6: Session Summary
Read ~/.claude/skills/wrapup/summary-template.md for the output format.
Examples
/wrapup # Full wrapup with session review
/wrapup project:~/my-app # Finalize specific project
/wrapup noreview # Skip the reviewer agent (quick sessions)
/wrapup prune # Full prune analysis includedDoes 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.