<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rulesets/.ai/workflows/clean-todo.org, branch main</title>
<subtitle>Claude Code skills, rules, and language bundles
</subtitle>
<id>https://git.cjennings.net/rulesets/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/rulesets/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/'/>
<updated>2026-05-11T20:37:19+00:00</updated>
<entry>
<title>docs(workflows): add clean-todo workflow</title>
<updated>2026-05-11T20:37:19+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-11T20:37:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/rulesets/commit/?id=83d48bd320157f9390e95b266f224f307c9a5ac3'/>
<id>urn:sha1:83d48bd320157f9390e95b266f224f307c9a5ac3</id>
<content type='text'>
clean-todo is the manual entry point for tidying todo.org: it runs the hygiene pass, then --archive-done (relocate completed level-2 subtrees into "Resolved"), then summarizes what changed and leaves the diff uncommitted for review. The wrap-up flow already does both passes at session end; clean-todo runs them on demand. It's listed in INDEX.org under the usual trigger phrases.
</content>
</entry>
</feed>
