tidy-repo

Inventory scattered TODOs, loose docs, and orphan files, then propose a non-destructive migration plan.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill tidy-repo-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tidy-repo
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-tasks/skills/tidy-repo
Command: npx skills add https://github.com/toderian/project_template --skill tidy-repo-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories that have grown unruly accumulate ad-hoc TODO files, inline TODO/FIXME comments, stray documentation outside docs/, and orphan files nobody remembers. Manually auditing and reorganizing this mess is tedious and risky, since a wrong move can lose history or delete something still needed. ## Core Features & Use Cases - Read-only audit: Sweeps the repo for loose work (TODO.md, NOTES.md, inline TODO:/FIXME: clusters), loose docs outside docs/, and orphan files (*.bak, scratch scripts, dead configs), respecting .gitignore and skipping generated output. - Timestamped migration report: Writes a reviewable report to docs/resources/_reports/tidy-repo/ with proposed I-NNN inbox ids, destination mappings, and a delta against the previous report, then stops for explicit user approval before changing anything. - Non-destructive apply: After approval, creates well-formed inbox idea files, moves docs with git mv to preserve history, only flags orphans (never deletes), and reconciles ledgers with at ledger. - Use Case: You inherit a repo with a root TODO.md, design notes scattered in notes/, and old backup scripts. Run the tidy to get a full inventory and migration plan, approve it, and end with everything sorted into docs/tasks_manager/_inbox/ and docs/resources/ ready for triage. ## Quick Start Ask the agent to tidy this repo by inventorying scattered TODOs, loose docs, and orphan files and proposing a migration plan into docs/tasks_manager and docs/resources.

Frequently Asked Questions about tidy-repo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up scattered TODO files in a repository?

Run a tidy pass that audits the repo for TODO.md files, inline TODO/FIXME comments, and loose notes, then proposes moving them into a docs/tasks_manager/_inbox/ as I-NNN idea files. Nothing moves until you approve the migration report.

How to organize loose markdown docs into a docs folder?

The audit finds markdown files outside docs/ (excluding root README, CHANGELOG, LICENSE, AGENTS.md, CLAUDE.md) and proposes moving them into docs/resources/ using git mv so file history is preserved. Broken inbound links are noted in the report.

Does the tidy process delete orphan or stale files?

No, orphan files such as *.bak, scratch scripts, and dead configs are only flagged in the report for your decision. Nothing is ever deleted; if you rule on an orphan, the preferred action is archiving rather than deletion.

Can I review the cleanup plan before any files are moved?

Yes, the workflow is propose-then-apply. A timestamped report is written to docs/resources/_reports/tidy-repo/ listing every proposed move, and the process stops until you explicitly approve, edit, or skip categories.

What happens to inline TODO comments in source code?

Inline TODO:/FIXME: comments are captured as inbox idea entries, but the comments themselves are left in place in the source code unless you explicitly ask for them to be stripped. Rewriting source is outside the tidy's scope.