How do I install the Tidy Project skill?

Run npx skillmds@latest add tzachbon/tidy-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tidy Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tidy Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tidy Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tidy Project?

tzachbon (@tzachbon) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tidy Project by tzachbon — Agent Skill

Name: Tidy Project
Author: tzachbon

Tidy Project

Use periodically (session start, or after a batch of changes) to keep a project clean. Triggers include "tidy the project", "clean up", janitor pass, or an AGENTS.md directive to run a cleanup occasionally. Handles stray log/tmp files, stale tasks, dead memory pointers, and AGENTS.md index drift.

tzachbon f1e2ed3 2.2 KB Updated Sep 17, 2026

File contents

tidy-project

A janitor pass. Scan the project for rot, fix what is clearly safe, propose what is risky, then commit. The project keeps everything tracked, so the tree should be clean and committed when you finish.

Core principle: a destructive step never runs unattended. Safe fixes apply automatically; anything that deletes tracked content or is ambiguous is proposed and waits for a yes.

Scan list

Stray junk — *.log, tmp/, .scratch/, editor/OS cruft, build leftovers.
TASKS.md staleness — completed items lingering in Now/Next; resolved Open Questions still listed.
Dead docs/memory/ pointers — MEMORY.md lines pointing at files that no longer exist (or files with no pointer).
AGENTS.md index drift — index entries for dirs/files that no longer exist, or top-level dirs/files missing from the index.
Broken cross-references — links between docs (CONTEXT, ADRs, TASKS) whose targets moved or were deleted.

Two classes

Safe (auto-fix):

Delete junk that already matches .gitignore patterns.
Fix an index entry whose target merely moved.
Remove a MEMORY.md pointer to a deleted file.
Repair a broken link whose target is unambiguous.

Risky (propose, then wait):

Deleting any tracked file.
Removing or rewriting a TASKS.md item (you might still want it).
Anything where "is this outdated?" is a judgment call.

Steps

Run the scan. Build two lists: safe-fixes, risky-proposals.
Apply the safe fixes.
Present the risky list as a short numbered plan. Apply only what the user approves.
Commit: git add -A && git commit -m "tidy: <summary>". If nothing changed, say so and skip the commit.

Do not

Delete tracked content without explicit approval.
"Tidy" by deleting work you do not understand. When unsure, propose, never auto.

---name: tidy-projectdescription: Use periodically (session start, or after a batch of changes) to keep a project clean. Triggers include "tidy the project", "clean up", janitor pass, or an AGENTS.md directive to run a cleanup occasionally. Handles stray log/tmp files, stale tasks, dead memory pointers, and AGENTS.md index drift.---# tidy-projectA janitor pass. Scan the project for rot, fix what is clearly safe, propose whatis risky, then commit. The project keeps everything tracked, so the tree shouldbe clean and committed when you finish.**Core principle:** a destructive step never runs unattended. Safe fixes applyautomatically; anything that deletes tracked content or is ambiguous is proposedand waits for a yes.## Scan list1. **Stray junk** — `*.log`, `tmp/`, `.scratch/`, editor/OS cruft, build leftovers.2. **`TASKS.md` staleness** — completed items lingering in Now/Next; resolved Open Questions still listed.3. **Dead `docs/memory/` pointers** — `MEMORY.md` lines pointing at files that no longer exist (or files with no pointer).4. **AGENTS.md index drift** — index entries for dirs/files that no longer exist, or top-level dirs/files missing from the index.5. **Broken cross-references** — links between docs (CONTEXT, ADRs, TASKS) whose targets moved or were deleted.## Two classes**Safe (auto-fix):**- Delete junk that already matches `.gitignore` patterns.- Fix an index entry whose target merely moved.- Remove a `MEMORY.md` pointer to a deleted file.- Repair a broken link whose target is unambiguous.**Risky (propose, then wait):**- Deleting any tracked file.- Removing or rewriting a `TASKS.md` item (you might still want it).- Anything where "is this outdated?" is a judgment call.## Steps1. Run the scan. Build two lists: safe-fixes, risky-proposals.2. Apply the safe fixes.3. Present the risky list as a short numbered plan. Apply only what the user approves.4. Commit: `git add -A && git commit -m "tidy: <summary>"`. If nothing changed, say so and skip the commit.## Do not- Delete tracked content without explicit approval.- "Tidy" by deleting work you do not understand. When unsure, propose, never auto.

Frequently asked questions