update-todos
Skill8 starsChanged 8 months agoMITView on GitHub
Interactive todo review. Walk through open items, get status updates, update the file.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- cypher0n3/dotagentstheir own version, first seen Nov 16, 2026
- not-manu/skillstheir own version, first seen Jul 6, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- cypher0n3/dotagents★ 3same name
- not-manu/skills★ 1same 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.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read todos/YYYY-MM-DD/todos.md for today's date.
- Distinctive: line 42
Update the todo file. Do NOT commit — the user may want to make more changes.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/update-todos - Interactive Todo Review
Step 1: Load Today's Todos
Read todos/YYYY-MM-DD/todos.md for today's date. If it doesn't exist, ask if the user wants to create one.
Step 2: Present Open Items
Show all unchecked items as a numbered list:
Here are your open items:
1. [HIGH] Task description
2. [HIGH] Another task
3. [MED] Medium priority task
4. [LOW] Low priority task
What's the status? You can say things like:
- "1 done" / "1,2 done"
- "3 blocked on X"
- "4 drop"
- "move 3 to high"
- "add: new task description"Step 3: Process Updates
For each update:
- done -> mark
- [x] ~~text~~ - blocked -> add "(blocked: reason)" to the item
- drop -> remove the item
- move -> move to the specified priority section
- add -> add new item to the specified (or default medium) priority
Step 4: Save
Update the todo file. Do NOT commit — the user may want to make more changes.
Show the updated summary: "Updated X items. Y remaining."
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.

