agentleFS
Sign inStart free
RevealUIStudioRevealUIStudio/revskills/skills/revealui-cleanup/SKILL.md

revealui-cleanup

Skill2 starsChanged 52 days agoMITView on GitHub

One-off session residue cleanup. Alias /cleanup. Runs the GAP-314 cleanup-session workflow (tmpscript sweep, workboard-sweep, worktree triage, unpushed/memory/scratchpad). Default is report-only; --fix is gated. Also runs from /checkpoint after prepare-for-exit (no --fix). Not /recover. Not /ops list.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not call cleanup-session.js directly from this skill — go through the runner.

    line 58
  2. Very specific:

    Do not pass --fix from /checkpoint.

    line 59
  3. Distinctive:

    Do not remove UNKNOWN or PR-OPEN worktrees.

    line 60
  4. Very specific:

    Do not treat this as /recover (crash inventory) or /rollup (MASTER_HANDOFF regen).

    line 61

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

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

Cleanup (/cleanup) — session residue

Thin one-off onto the registered workflow cleanup-session ($JV_REPO/workflows/cleanup-session.yml). Delegates to workflow-run.js. Does not reimplement sweeps or safety classes.

Load helpers:

. "$REVEALFLEET_ROOT/revskills/scripts/lib/session-state.sh"

Default (report)

node "$JV_REPO/scripts/workflow-run.js" cleanup-session

Runs the report-first arm, then STOPPED-GATED on the destructive arm. Print the runner output. Do not pass --fix unless the user asked to apply gated cleanup.

Apply gated arms (/cleanup --fix)

Tell the user the gated step deletes expired temp scripts and removes only SAFE-TO-REMOVE worktrees (terminal PR + clean + no unpushed). Then:

node "$JV_REPO/scripts/workflow-run.js" cleanup-session --fix

--dry-run prints the plan and executes nothing.

Where this already runs

SurfaceHow
/checkpoint Step 5c2Same runner, no --fix
/ops cleanup-sessionSame workflow by name
prepare-for-exitOverlapping read-only checks only; not a substitute

Do not

  • Do not call cleanup-session.js directly from this skill — go through the runner.
  • Do not pass --fix from /checkpoint.
  • Do not remove UNKNOWN or PR-OPEN worktrees.
  • Do not treat this as /recover (crash inventory) or /rollup (MASTER_HANDOFF regen).

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free