agentleFS
Sign inStart free
ryanportfolioryanportfolio/Harness-Firmware/.claude/skills/wrapup/SKILL.md

wrapup

Skill1 starsChanged 21 days agoMITView on GitHub

Use on /wrapup or when the user asks if a session is done, good to archive, or what is left: one verdict from git, the PR, scratch files and running servers or browsers.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Distinctive:

    Add what only this session knows: browsers opened through MCP tools, background tasks or agents still running, task chips you offered, …

    line 16

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wrap up

Answer "good to archive?" from evidence, not memory. Read-only until the user agrees to a fix. Script paths are from the repository root; when this skill came from a plugin, use the scripts/ folder in this skill's base directory instead, and keep running from the checkout. It needs the servers skill installed beside it.

  1. From the session's checkout, run node .claude/skills/wrapup/scripts/wrapup.mjs. Add --worktrees when the user asks about cleanup across the repo. It fetches, then reports:
    • uncommitted changes and commits that are on no remote;
    • this branch's PR and its state;
    • .tmp/ scratch that removing the worktree would delete;
    • servers and automation browsers still running from this checkout (through .claude/skills/servers/scripts/servers.mjs);
    • other worktrees of the repo: holding work, or sitting exactly on a merged PR head and removable.
  2. Add what only this session knows: browsers opened through MCP tools, background tasks or agents still running, task chips you offered, worktrees you created by hand, and promises made earlier in the conversation that are not done.
  3. Reply with the verdict first, one line: Ready to archive, or Not yet, then each blocker with the action that clears it (commit and push, merge or close PR #N, stop the server on :PORT, copy .tmp/ findings somewhere durable). Notes that do not block go after, briefly. An open PR blocks: the session is not ready to archive until its PR is merged or closed. That includes PRs this session opened from other worktrees or repositories, which the script cannot see.
  4. Offer the fixes as one go. With the user's yes: push, close the servers and browsers this session started (node .claude/skills/servers/scripts/servers.mjs close <port> --yes), and remove only worktrees this session created, after removing their node_modules links with rmdir. Never git worktree remove --force through a junction, never delete other sessions' worktrees, never discard uncommitted work.

A merged PR with leftover local commits is a note, not a pass: check that those commits were part of the merge before saying ready.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free