todo-archive
Skill6 starsChanged 6 days agoMITView on GitHub
Archive checked `.ai/TODO.md` tasks into `.ai/todos/YYYY-MM/DD.md`, leaving unchecked tasks.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- PaulRBerg/agent-skillsword for word, first seen Oct 24, 2026
- bordenet/superpowers-plustheir own version, first seen May 3, 2026
Other versions2 projects use a version of this.
Word for word · 1
- PaulRBerg/agent-skills★ 104100% same
Edited · 0
None found.
Wrote their own version · 1
- bordenet/superpowers-plus★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-brainSkill
- agents-docsSkill
- agents-introspectionSkill
- agents-systemSkill
- ai-pruneSkill
- apple-device-integrationSkill
- brainstorm-with-meSkill
- chromium-browserSkill
- cli-castSkill
- cli-coingeckoSkill
- cli-ghSkill
- cli-justSkill
- codebase-designSkill
- code-polishSkill
- commitSkill
- copy-transcript-pathSkill
- effect-tsSkill
- evm-atlasSkill
- fresh-eyes-sweepSkill
- frontend-designSkill
- grill-meSkill
- html-playgroundSkill
- interview-meSkill
- large-file-refactorSkill
- naming-refactorSkill
- node-deps-bumperSkill
- orchestrationSkill
- pdfSkill
- release-bumperSkill
- repo-fanoutSkill
- repo-harmonizationSkill
- repo-renameSkill
- retroSkill
- skill-harmonizationSkill
- social-mediaSkill
- spreadsheetsSkill
- tailwind-cssSkill
- task-handoffSkill
- tool-finderSkill
- vitestSkill
- wrap-upSkill
- writing-editorSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
If a slash or dollar invocation already added these instructions to the conversation, follow them directly.
- Very specific: line 37
Verify .ai/TODO.md exists under the root.
- Very specific: line 50
If --hint matches no heading, the helper exits non-zero and lists the available sections.
- Very specific: line 52
If useful, inspect only <repo_root>/.ai/TODO.md and the exact archive path returned by the helper.
- Distinctive: line 75
Do not repeat full dry-run document content in the final message or add decoration to TODO/archive files, paths, commands, or helper …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TODO Archive
If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool.
Arguments
path(optional): Repository root or any path inside the repository. Default to the current directory.--hint TEXT(optional): Archive only the section whose heading containsTEXT(case-insensitive substring), including its subsections. Without it, archive checked tasks from the whole file. Checked tasks outside the matched section stay in.ai/TODO.md.--date YYYY-MM-DD|YYYY_MM_DD(optional): Archive date. Default to today's local date.--dry-run(optional): Preview target paths and rendered content without writing.
Workflow
Resolve the supplied
path, or the current directory when omitted. For an existing file, use its containing directory. For a directory, use that directory. Store the absolute directory asstart_dir, then resolve its Git root:git -C "$start_dir" rev-parse --show-toplevelStore the result as
repo_root. Whenstart_diris outside a Git repository, use it asrepo_root. Stop on a missing input path or another resolution error.- Verify
.ai/TODO.mdexists under the root. If it is missing, stop and report the path checked. Resolve the skill directory and run its helper:
uv run python "<skill-dir>/scripts/archive_todo.py" --root "$repo_root"Pass through
--hint,--date, or--dry-runwhen the user requested them.- Report the rewritten
.ai/TODO.md, the created or merged archive path, the matched section (when--hintwas given), and the archived/remaining task counts. If an archive for the date already exists, the helper appends the new batch to it, retaining one matching top-level heading. If the helper reports no checked tasks, treat it as a no-op. If--hintmatches no heading, the helper exits non-zero and lists the available sections. In that case, relay them. - If useful, inspect only
<repo_root>/.ai/TODO.mdand the exact archive path returned by the helper. Verify their contents directly. When Git ignores them, compare filesystem snapshots rather than relying ongit diff.
Helper Behavior
scripts/archive_todo.py reads <root>/.ai/TODO.md and any existing archive for the date, writes archived tasks to
<root>/.ai/todos/YYYY-MM/DD.md, and rewrites <root>/.ai/TODO.md with the remaining tasks. It preserves task-free
sections and prose verbatim (a minimal stub with the source's first heading, or # TODO, only if everything was
archived). With --hint, it restricts archiving to the matched heading's subtree and exits non-zero listing available
headings when nothing matches. A same-day re-run appends its batch to that day's file, removing the new leading H1 only
when it exactly matches the existing archive's leading H1.
Completion
Completion evidence is the helper's archive path plus archived and remaining task counts. A no-checked-task result is a
successful no-op. Dry-run completion requires rendered paths/content with no filesystem changes, but the final message
still follows the one-line formats below. Report the result as a single line (append a (scope: "<hint>") segment only
when --hint was given), with the archive path relative to the repository root:
- Success:
📦 Archived <n> → <archive path> (created|merged) · <remaining> remaining - No-op:
✅ Nothing to archive · <remaining> remaining - Dry run:
🔎 Would archive <n> → <archive path> (would create|would merge) · <remaining> would remain
Do not repeat full dry-run document content in the final message or add decoration to TODO/archive files, paths, commands, or helper diagnostics.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

