/clean-artifacts

Sweep workflow exhaust from the repo (stale verify markers, old Playwright screenshots, expired SDLC traces). Strict allowlist; never touches git-tracked files or critical artifacts. Dry-run by default. Runs standalone or via /session-end.

Copy the command

/clean-artifacts

Type it bare, or paste it with loose context after — Claude figures out the rest.

Solves

Workflow exhaust piles up — stale verify markers, old screenshots, expired SDLC traces.

Payoff

Sweeps three classes of exhaust from the working tree. Idempotent. Safe by exclusion list.

Takes in

Optional --dry-run flag

Returns

Files removed by class
Skipped safety-list entries
Total space reclaimed

Runs with

—

Needs first

—

Called by

—

Deep dive — 3 sections · ~254 words · original SKILL.mdScroll for tutorial ↓

What it does

Over time, bassclef-substrate repos accumulate workflow exhaust in predictable locations:

None of these are load-bearing once their session ends. None are git-tracked (all covered by .gitignore). But without an explicit sweep, they rot in place.

Read the full skill

The complete instructions live at .claude/skills/clean-artifacts/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.

Where in the SDLC

Why this phase: Sweep workflow exhaust from the repo — stale verify markers, old Playwright screenshots, expired SDLC traces. Runs standalone or via /session-end.

Skills catalog — browse all skills grouped by lifecycle phase
Tier system — what each tier gives you

FAQ

Terms from bassclef vocabulary that appear on this page.

load-bearing: A part of the system that other parts depend on — remove it and downstream things break. Bassclef uses the word for artifacts that other artifacts read: a canvas is load-bearing when a spec cites it, a spec is load-bearing when Builder uses it. Plain equivalent: 'actually used' or 'counted on'.
chronicle: A narrative log of what a session shipped — what worked, what did not, what got deferred. Written at session-end. Bassclef's chronicles live under `docs/chronicles/YYYY-MM-DD-slug.md`. Chronicles are how future sessions understand context that the code alone cannot show. See: /docs/skills/session-log
whereami: The authoritative project-state snapshot — current phase, active goals, subsystem status, gate progress, session recap history. Read at session-start; updated at session-end. The one file every new session should read first to know where the project stands. See: /docs/skills/whereami
hook: A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
rule: A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
skill: A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.

Shipped by @kingofrock · Read the essays