todos-cleanup

Classify backlog todos as DONE, PARTIAL, or OPEN using git history.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill todos-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todos-cleanup
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/solopreneur/skills/todos-cleanup
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill todos-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch cleanup of backlog todos by classifying items based on git history, then moving them to done/doing or leaving open as needed.

Core Features & Use Cases

  • Classify backlog items by analyzing related commits to determine completion status.
  • Automatically propose target directories (done, doing) for items and preserve original files.
  • Resolve backlog paths from plugin config or project structure to enable automated scanning.

Quick Start

Run the skill against your backlog directory to classify items and propose moves to done (for fully implemented) or doing (partial progress) after review.

Frequently Asked Questions about todos-cleanup

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

FAQPage Schema
How do I automate backlog triage using git history evidence?

Automating backlog triage involves analyzing git commit history to classify todos as DONE, PARTIAL, or OPEN, then moving items to organized status subdirectories like done or doing for progress tracking after user confirmation.

What is the best way to classify and organize stale backlog todos in a project?

Classifying stale backlog todos requires scanning backlog-like directories and evaluating related commits to determine completion status, preserving original files by moving them to done or doing folders rather than deleting them.

How does git history analysis determine if a backlog item is fully implemented?

Git history analysis determines implementation status by evaluating related commits to find evidence of completion, categorizing items as DONE for full implementation, PARTIAL for ongoing work, or OPEN if no progress is found.

Do I need to configure a specific path for the tool to scan my backlog directory?

You do not need strict path configuration because the tool resolves backlog locations from plugin config or automatically discovers them through the project structure to enable automated scanning.

Can I safely move backlog items to done or doing folders without losing original files?

You can safely move backlog items because the process requires no file deletion, strictly moving items to corresponding status subdirectories for organized review and progress tracking after explicit user confirmation.

What happens to backlog todos that show no git commit progress?

Backlog todos with no git commit progress are classified as OPEN and remain in their original location, while items with full or partial implementation are proposed for movement to done or doing subdirectories.