Skip to content
Skills Library
Programming · Review & audit

clean

/clean

Use when the human requests cleanup, before delivering work, or before committing changes to review relevant leftovers, stale references and project guidance.

Repository
skills ↗
Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the human requests cleanup, before delivering work, or before committing changes to review relevant leftovers, stale references and project guidance.

Original author description

Use when the human requests cleanup, before delivering work, or before committing changes to review relevant leftovers, stale references and project guidance.

How it works

  1. Choose the scope
  2. Clean with evidence
  3. Verify and report
Original SKILL.md headings · 23 lines, 502 words
SKILL.md preview
---
name: clean
description: "Use when the human requests cleanup, before delivering work, or before committing changes to review relevant leftovers, stale references and project guidance."
---

# Clean

Leave the relevant work coherent and remove verified leftovers without disturbing the human's work. Cleanup requires judgment: a hook can request this review, but cannot decide on its own which files or evidence are safe to remove.

## Choose the scope

1. Identify the current request and applicable scope. Before delivery, make a quick applicability check; if the task changed no files and produced no artifacts requiring cleanup, skip further review. Otherwise review the relevant work from the current task. Before a commit, inspect the proposed commit and surrounding repository, documentation and agentic setup broadly enough to spot cleanup needs. Clean only the intended scope and report material unrelated findings. An explicit cleanup request sets its own scope.
2. Check the current working tree and staged changes where applicable. Separate pre-existing or unrelated changes from material created by the current work. Preserve the human's files, active plans, handoffs, historical decisions, useful evidence, licenses and artifacts unless the human authorized their removal. Do not automatically stage unrelated changes.

## Clean with evidence

3. Look for the task's temporary files in `.work/temp/` and check for unused artifacts, redundant output, obsolete paths, broken links and stale guidance within scope. Check whether each candidate still has a purpose. A file is not disposable merely because it is untracked, old, generated or unfamiliar. Preserve files whose purpose or safe removal is uncertain, and report material uncertainty.
4. Remove a leftover only when its ownership, obsolescence and safe removal are clear within the authorized task. Repair task-related stale references and documentation when evidence supports the correction; update project-specific agent instructions or artifacts when the work made them inaccurate. Preserve historical records as history rather than rewriting or deleting evidence that remains useful.
5. Before an authorized removal of important, hard-to-recreate work, make and verify a targeted `.work/recover/` copy according to the [workspace rules](../../references/Workspace.md). Record the original location and restore instructions; skip recovery for reproducible leftovers. A recovery copy does not authorize deletion. If deletion or a broader change could affect unrelated work, user data or uncertain evidence, resolve that with the human first. If cleanup is not applicable, make no changes.

## Verify and report

6. Inspect the resulting diff and relevant paths. Use focused checks appropriate to the changes; confirm that updated references resolve and intended behavior or records are preserved. Report material cleanup, remaining uncertainty and any unavailable verification. Never claim a hook ran or cleanup occurred without evidence.
7. Before committing, review the intended changes and check the index for private `.work/` files; only explicitly authorized exceptions may be tracked. Preserve the human's staged and unstaged work. If Mirket's commit hook is active, acknowledge the review with `MIRKET_CLEANUP_DONE=1` on the standalone commit command and name the worktree with an absolute `git -C` path. A hook request does not authorize committing, staging, publishing or modifying unrelated content.

**Done:** Relevant leftovers and stale material have been addressed within the authorized scope, project guidance reflects the work, and uncertain or preserved items are reported when material.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · nazmirket/skills90MIT
lucastamoios/skills100MIT
kurtosis-tech/kurtosis95Apache-2.0
bkhtmm/cLEAN90MIT
anilsoylu/famiglia90Apache-2.0
melodic-software/claude-code-plugins84MIT

Database snapshot: 13.11.2026 · package version 8b35b9fdde5b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100branch-cleanup
    Clean up merged and stale branches from local and remote repositories. Use when branch list is cluttered or after merging PRs.
  • 100code-review-gate
    Use when code has been written, before committing, or when merging a PR; also when the user says "review my code", "check before commit", "take a look at this change", "PR review", or asks for a strict review/merge gate.
  • 90code-review
    Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
  • 90review
    Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.
  • 95triage-repo-cleanup
    Triage and clean up a repo's leftovers — stale git worktrees, merged and abandoned local branches, stale remote-tracking refs, and old stashes — by classifying each one by whether deleting it would destroy work. Triggers on: clean up my branches, clean up leftover worktrees,…
  • 90clean-clean-cut
    Use when asked to run /clean-clean-cut to cut accumulated records and residue. Not for untracked or non-VCS changes, or branch/worktree cleanup: use git-cleanup.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.