Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/.
Install Todos Cleanup
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hanamizuki/solopreneur todos-cleanup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .claude/skills/todos-cleanup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .claude/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hanamizuki/solopreneur todos-cleanup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .agents/skills/todos-cleanup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .agents/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hanamizuki/solopreneur todos-cleanup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .cursor/skills/todos-cleanup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .cursor/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hanamizuki/solopreneur.git --path skills/solopreneur/todos-cleanup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hanamizuki/solopreneur todos-cleanup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .gemini/skills/todos-cleanup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .gemini/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hanamizuki/solopreneur todos-cleanupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .github/skills/todos-cleanup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .github/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hanamizuki/solopreneur --skill todos-cleanup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hanamizuki/solopreneur todos-cleanup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/solopreneur/todos-cleanup .opencode/skills/todos-cleanup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "todos-cleanup" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/solopreneur/todos-cleanup into .opencode/skills/todos-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "todos-cleanup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
todos-cleanup- GitHub stars
- 152
- Token cost
- ~1.5k tokens
- SKILL.md length
- 306 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/.
- Works in 4 steps: Gather file list → Spawn sonnet subagent for analysis → Present results and confirm → …
- The user says cleanup todos
- SKILL.md covers Config Discovery, Classification Rules, Workflow and Important
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Todos Cleanup is an agent skill from hanamizuki/solopreneur. Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/. Use when the user says "cleanup todos", "triage backlog", "clean up backlog", "check todos status", or wants to classify backlog items based on actual implementation status.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow. The repository describes itself as: Skills and agents for solopreneurs — ship, review, debug, and think through problems with AI. The licence is MIT.
When your agent uses it
- The user says cleanup todos
- Clean up backlog
- Check todos status
- Wants to classify backlog items based on actual implementation status
Example prompts
- “cleanup todos”
- “triage backlog”
- “clean up backlog”
- “/todos-cleanup”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f43f001. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Todos Cleanup loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 306 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hanamizuki/solopreneur at commit f43f001, republished under its MIT licence (© hanamizuki). 306 words, ~1,516 tokens.
Download SKILL.mdSave it as
.claude/skills/todos-cleanup/SKILL.md (or your agent's skills folder).- name
- todos-cleanup
- description
- Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/. Use when the user says "cleanup todos", "triage backlog", "clean up backlog", "check todos status", or wants to classify backlog items based on actual implementation status.
Todos Cleanup
Scan the backlog directory and classify each item by checking git history for related commits. Present findings for user confirmation, then move files.
Config Discovery
Before scanning, resolve the todo directory paths. Source the config helpers first:
# --- solopreneur config helpers (sourced from shared/config.sh) ---
# One real shell file, so no harness rewrites the helpers on the way to the
# shell. Claude Code replaces the ${CLAUDE_SKILL_DIR} token below when it loads
# this body; Codex does not. It is SINGLE-quoted on purpose — it is a load-time
# token, not an environment variable, and letting the shell expand the name
# would source whatever an inherited value happened to point at. Unreplaced, it
# is not a directory, so substitute the absolute path of the directory holding
# THIS SKILL.md — every harness states that path to the model.
SOLO_SKILL_DIR='${CLAUDE_SKILL_DIR}'
[ -d "$SOLO_SKILL_DIR" ] || SOLO_SKILL_DIR="<absolute path of the directory holding this SKILL.md>"
SOLO_CONFIG_SH="$SOLO_SKILL_DIR/../../shared/config.sh"
# Three candidates, one contract. Inside the plugin the helpers sit at ../../shared/;
# authoring against this repo reaches them under src/solopreneur/shared/; and a
# skill republished on its own — any flattened skills directory — carries them
# at scripts/config.sh instead, because shared/ is a sibling of skills/ and does
# not travel with a per-skill copy. Try each in order, then STOP. Sourcing a
# file that is not there does not halt the shell: every helper stays undefined,
# every config read returns empty, and the 2026-08-11 A2 run showed where that
# leads — the model "rescued" it with a repo-relative path, which resolves only
# when the repo under review happens to be this plugin's own source repo.
# Canonical authoring keeps non-skill source under src/.
[ -f "$SOLO_CONFIG_SH" ] || SOLO_CONFIG_SH="$SOLO_SKILL_DIR/../../../src/solopreneur/shared/config.sh"
[ -f "$SOLO_CONFIG_SH" ] || SOLO_CONFIG_SH="$SOLO_SKILL_DIR/scripts/config.sh"
[ -f "$SOLO_CONFIG_SH" ] || { echo "HALT: solopreneur config helpers not found under $SOLO_SKILL_DIR — stop here, do not improvise a path"; exit 1; }
source "$SOLO_CONFIG_SH"
# --- end solopreneur config helpers ---Check plugin config:
bash read_solopreneur_config todosIf the
todoskey exists, use itsbacklog,done,doing,latervalues.If no config — scan the project: Search for directories that look like todo/task storage:
bash # Common patterns find . -maxdepth 3 -type d \( -name "todos" -o -name "todo" -o -name "TODO" \ -o -name "backlog" -o -name "tasks" -o -name ".todos" \) 2>/dev/nullFor each candidate, count
.mdfiles inside. Present findings:Found potential todo directories: a) todos/backlog/ (12 .md files) b) tasks/ (5 .md files) Which is your backlog directory? (or enter a custom path)Save to config after user confirms. Discovered paths are repo-relative (
todos/backlogetc.), so the per-repo write helper anchors them to this repo's entry:bash write_solopreneur_repo_config todos '{ "backlog": "todos/backlog", "done": "todos/done", "doing": "todos/doing", "later": "todos/later" }'Substitute user-confirmed paths into the JSON. Each repo gets its own entry — running this skill in a different repo will not clobber this one's setting.
Use the resolved paths for all subsequent steps. Variables below:
$BACKLOG— backlog directory (e.g.,todos/backlog)$DONE— done directory (e.g.,todos/done)$DOING— doing directory (e.g.,todos/doing)
Show full SKILL.md (153 more words)Show less
Classification Rules
| Status | Criteria | Action |
|---|---|---|
| DONE | Found commits that fully implement the todo's requirements | Move to $DONE |
| PARTIAL | Some related commits exist, but not all requirements met | Move to $DOING |
| OPEN | No related commits found | Stay in $BACKLOG |
Workflow
Step 1: Gather file list
List all .md files in $BACKLOG. If empty, tell the user and stop.
Step 2: Spawn sonnet subagent for analysis
Spawn a single sonnet subagent (model: "sonnet") with this prompt:
Read each todo file in {$BACKLOG} and determine its implementation status
by searching git history. For each file:
1. Read the file to understand what the task requires
2. Extract 3-5 search keywords from the title and content
3. Run `git log --oneline --all --grep="keyword"` for each keyword
4. If commits are found, read the commit messages to judge completeness
5. Classify as DONE / PARTIAL / OPEN
Files to check:
[list of file paths]
Report a markdown table:
| File | Status | Evidence |
|------|--------|----------|
| filename.md | DONE/PARTIAL/OPEN | commit hash + message, or "no related commits" |
Be conservative — only mark DONE if the commits clearly cover the full scope
described in the todo. If unsure, mark PARTIAL.Step 3: Present results and confirm
Show the subagent's table to the user. Ask for confirmation before moving files. The user may override individual classifications.
Step 4: Move files
After confirmation:
- DONE items →
$DONE - PARTIAL items →
$DOING - OPEN items → no action
Create target directories if they don't exist.
Report the final state:
todos/
├── backlog/ (N files remaining)
├── doing/ (N files)
├── done/ (N files)
└── later/ (N files)Important
- Never delete todo files — only move them
- Always confirm with user before moving
- The subagent does research only — it must not modify or delete any files
© hanamizuki, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/solopreneur/todos-cleanup of hanamizuki/solopreneur.
Open the folder on GitHubat commit f43f001
Compare with similar skills
Todos Cleanup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Todos Cleanup this skillhanamizuki/solopreneur | 152 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Contextual Commit Messagesyamadashy/repomix | 29k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Contextual Commit Messages
yamadashy/repomix
Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.
Git Merge Conflict Resolver
tailcallhq/forgecode
Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.
More from hanamizuki/solopreneur
All 31 skills in this repoPreview
hanamizuki/solopreneur
Create an interactive HTML preview of any proposal, plan, idea, doc, brief, or spec and land it in the browsable local Preview Library by default (opens under file:// with a catalog sidebar and…
iOS Patterns
hanamizuki/solopreneur
A skill your agent uses when building iOS/macOS apps with SwiftUI — covers localization (String Catalogs), date/time formatting, JSON date decoding, Previews, state management, sheet/navigation…
Linkedin Growth
hanamizuki/solopreneur
LinkedIn organic growth consultant — diagnoses profiles, discusses goals, and co-creates a personalized 90-day growth plan.
Perspective
hanamizuki/solopreneur
Switch perspectives to think through problems using the mental models of ten iconic thinkers: Elon Musk, Richard Feynman, Charlie Munger, Naval Ravikant, Steve Jobs, Nassim Taleb, Ilya Sutskever…
Slide Design
hanamizuki/solopreneur
Create brand-aware presentations using frontend-slides or reveal.js.
X Growth
hanamizuki/solopreneur
X/Twitter growth consultant — diagnoses profiles, discusses goals, and co-creates a personalized growth plan.
Related
Categories
Questions about Todos Cleanup
What does Todos Cleanup do?
Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/. Todos Cleanup is an agent skill from hanamizuki/solopreneur. Batch cleanup of backlog todos — checks which items are already completed or partially done by searching git history, then moves them to done/ or doing/.
When should I use Todos Cleanup?
Todos Cleanup fits situations like: the user says cleanup todos; clean up backlog; check todos status; wants to classify backlog items based on actual implementation status.
How do I install Todos Cleanup in Claude Code?
Run `npx skills add hanamizuki/solopreneur --skill todos-cleanup -a claude-code`. Or copy the skill folder (skills/solopreneur/todos-cleanup in hanamizuki/solopreneur) into .claude/skills/todos-cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Todos Cleanup in Codex?
Run `npx skills add hanamizuki/solopreneur --skill todos-cleanup -a codex`. Or copy the skill folder (skills/solopreneur/todos-cleanup in hanamizuki/solopreneur) into .agents/skills/todos-cleanup in your project. Codex loads it when a task matches its description.
Can I use Todos Cleanup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hanamizuki/solopreneur --skill todos-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/todos-cleanup, .gemini/skills/todos-cleanup, .github/skills/todos-cleanup and .opencode/skills/todos-cleanup in your project.
What does Todos Cleanup need to run?
SKILL.md names no scripts, command-line tools or credentials: Todos Cleanup is instructions for the agent only.
Does Todos Cleanup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Todos Cleanup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Todos Cleanup use?
Todos Cleanup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Todos Cleanup use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Todos Cleanup?
Skills that share tags, products or a category with Todos Cleanup: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Todos Cleanup?
hanamizuki (a GitHub user) maintains it in hanamizuki/solopreneur, which has 152 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on September 26, 2026.
Source: hanamizuki/solopreneur on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.