agentsclimarketplace

Cleanup artifacts

Skill ethanaubuchon/dossier-tradecraft/skills/cleanup-artifacts

Claude Code workflow recipes built on dossier-mcp — research → design → scope → decompose → implement as overridable slash commands and skills.

Install
npx -y skills add ethanaubuchon/dossier-tradecraft --skill cleanup-artifacts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use in /implement at the draft→ready boundary, before publish-pr's squash, to delete this branch's transient plan/spec artifacts so they don't ship in the PR. Deletes .claude/plans/<branch>.md (flattened name). Distinct from repo-setup's prune of previously-merged branches' artifacts.

SKILL.md

1.9 KB, as published. Nobody here has run it

Cleanup Artifacts

Deletes this branch's transient working artifacts — the plan file and any spec scratch — at the draft→ready boundary, so they don't ship in the PR. One of /implement's two distinct cleanups:

  • repo-setup prunes previously-merged branches' worktrees + plan files (at setup).
  • cleanup-artifacts deletes this branch's plan file (at finalize).

Runs before publish-pr's squash.

Input

  • branch — the current feature branch.

Steps

  1. Delete this branch's plan file: rm -f .claude/plans/<branch>.md, using the /→- flattened branch name (feat/foo → .claude/plans/feat-foo.md, matching plan-file).
  2. Delete any other transient spec/scratch artifacts the project marks for this branch.

Output / contract

  • In: the branch.
  • Out: working tree with this branch's plan/spec artifacts removed.
  • Side effects: deletes the plan file. With the default gitignored plan location the deletion isn't part of the diff (pure housekeeping); if a project tracks plan files, the deletion is a real change — which is why it must run before publish-pr's squash, so it folds into the single commit (no plan file in PR history). publish-pr stages this deletion with git add -A before committing — without that staging the reset --soft index would re-commit the tracked plan file.

Project overrides

  • Plan-artifact location — a repo that stores plans/specs elsewhere (e.g. docs/plans/) overrides the path; keep the flatten rule consistent with plan-file and repo-setup.

Future scope

  • (none beyond per-project artifact locations.)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.