task-cleanup
Skill8 starsChanged 3 months agoMITView on GitHub
Archive or remove completed tasks from the task list. Use when task list grows large or to clean up after a project phase. Invoke with "/task-cleanup" or "clean up tasks". Triggers on "task-cleanup", "archive completed tasks", "clear completed tasks".
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cotSkill
- dependency-healthSkill
- hibernateSkill
- repo-docsSkill
- skill-builderSkill
- skill-validatorSkill
- template-upgradeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Before handing off to another session
- Distinctive: line 31
Keep pending and in_progress
- Distinctive: line 34
Only archive completed tasks older than 24 hours
- Distinctive: line 35
Keep recent completions for reference
- Distinctive: line 39
Use when starting completely fresh
- Distinctive: line 76
Use for housekeeping, not for hiding incomplete work
- Distinctive: line 77
Consider running weekly or at project milestones
≈ “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
Task Cleanup Skill
Manage task list hygiene by archiving or removing completed tasks.
When to Use
- Task list has many completed tasks cluttering the view
- End of a project phase or milestone
- Starting fresh on a new focus area
- Before handing off to another session
Execution Steps
1. Assess Current State
TaskList()
→ Count: pending, in_progress, completed
→ Identify tasks completed more than 24 hours ago2. Present Options
Option A: Archive All Completed
- Move all completed tasks to archive
- Keep pending and in_progress
Option B: Archive Old Completed
- Only archive completed tasks older than 24 hours
- Keep recent completions for reference
Option C: Full Reset
- Archive everything except in_progress
- Use when starting completely fresh
3. Execute Cleanup
For each task to archive:
TaskUpdate({
taskId: "<id>",
metadata: { archived: true, archivedAt: "<ISO-8601>" }
})Or mark completed with archive note:
TaskUpdate({
taskId: "<id>",
status: "completed",
description: "[ARCHIVED] " + original_description
})4. Report Results
## Task Cleanup Complete
**Before:** X total (Y pending, Z in_progress, W completed)
**After:** X total (Y pending, Z in_progress, 0 completed)
**Archived:** W tasks
Archive location: ~/.claude/tasks/{taskListId}/Notes
- Tasks are never truly deleted - metadata marks them archived
- Archived tasks don't appear in normal TaskList output
- Use for housekeeping, not for hiding incomplete work
- Consider running weekly or at project milestones
Created: 2026-01-23 Part of: Task Management System v2.1.16
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.

