Worktree Closeout
Use when the user asks for worktree closeout, branch closeout, parallel closeout, worktree janitor, 工作树收口, 分支收口, or 并行收口, especially when work spans multiple Codex sessions and you need a date-based scan of open worktrees, closeout status, suggested merge/prune order, and prompt-ready handoff instructions.
Install
npx skills add leonsong09/worktree-closeout --skill worktree-closeoutgit clone --depth 1 https://github.com/leonsong09/worktree-closeout.git /tmp/worktree-closeout
mkdir -p ~/.claude/skills
cp -r /tmp/worktree-closeout/. ~/.claude/skills/worktree-closeoutPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# worktree-closeout ## Overview Read-only closeout triage for Codex work that spans multiple sessions, branches, or worktrees. This skill does **not** auto-merge, auto-delete, auto-push, or auto-prune. It asks for a date and scope, runs the scanner, reads the generated artifact, then turns that artifact into a chat summary, a suggested closeout order, and prompt-ready handoff instructions. ## When to Use - User wants to know which worktrees or branches still need 收口 - Work was split across multiple sessions and the current status is unclear - You need a date-based scan before deciding merge / keep / prune actions - You want a controller prompt plus per-item prompts for closeout follow-up ## When Not to Use - **Single current session wrap-up:** use `session-wrap` - **Same-day project report:** use `project-daily-summary` - **Single branch is already chosen for final handling:** use `finishing-a-development-branch` - **Dangerous branch actions:** do not use this skill as permission to merge, delete, prune, or push automatically `project-daily-summary` may optionally call this skill when the user wants a **same-day all-repo summary with a closeout appendix**. ## Required Flow ### 1. Ask for the date first Always resolve the date before asking anything else. - Accept `YYYY-MM-DD` or a relative day such as “昨天” - Restate the resolved **exact date** - If the user already supplied a clear date, confirm it instead of inventing a different one
Details
- Skill name
worktree-closeout- Repository
- leonsong09/worktree-closeout
- License
- MIT
- Repo updated
- 30 March 2026
FAQ
What does the Worktree Closeout skill do?
Use when the user asks for worktree closeout, branch closeout, parallel closeout, worktree janitor, 工作树收口, 分支收口, or 并行收口, especially when work spans multiple Codex sessions and you need a date-based scan of open worktrees, closeout status, suggested merge/prune order, and prompt-ready handoff instructions.
How do I install the Worktree Closeout skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add leonsong09/worktree-closeout --skill worktree-closeout. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Worktree Closeout popular?
It lives in leonsong09/worktree-closeout, which has 6 GitHub stars and 2 forks.
Related skills
Blitz
6ADM-NKH/claude-blitz
A continuously-firing background work runner for Claude Code. Queue real tasks ("/blitz add"), track long-term goals ("/blitz goal add"), and enable per-project audit rotations ("/blitz audit enable"). Blitz fires on a configurable cadence with a per-project idle gate, decomposes goals into increments on a long-lived branch, and persists every fire's output to ~/blitz/runs/<timestamp>/. Includes commands to manage the backlog, goals, audits, schedules, and kill switches (off/on/skip).
Limit Up Dao
6laozdao/limit-up-dao
老子道涨停股批量归因分析Skill。基于开源大模型,输入日期自动获取当日所有涨停股票数据,逐一输出多维度归因分析报告。GitHub https://github.com/laozdao/limit-up-dao。触发场景:用户要求分析某日涨停股、批量涨停归因、今日涨停复盘、涨停板原因分析、连板股分析等。
Auto Experiment
5zxl696/smallmodel-auto-experiment-skill
自动化超参数/架构搜索循环。给定模型代码、数据集和优化目标,自动生成 train.py,经双 agent 审计门禁通过后,循环调用 DeepSeek 提出改进建议、训练、用 git 追踪每轮变更,保留最优配置和 checkpoint。
Should I Contribute
8definitelynotchirag/should-i-contribute
Research any open-source repository end to end and answer the core question — SHOULD YOU contribute to it? — with a GO / NO-GO / GO-IF verdict backed by evidence: snapshot, momentum, contribution landscape (PR acceptance rates, outside-contributor merge rates, first-timer outcomes), issue health, governance, community sentiment, and a final go/no-go recommendation. Use when the user asks 'should I contribute to X', wants a before-I-contribute due-diligence check on a project, asks whether a project accepts outside PRs, wants contribution-health numbers like PR merge rates or stale-PR counts, o
Gitlab Skill
5ekohe/gitlab-skill
GitLab integration for fetching issues/MRs, generating executive summaries, performing comprehensive code reviews, and automating issue resolution workflows. Use when working with GitLab issues, merge requests, or when asked to summarize, review, comment on, or resolve GitLab work items.
Github Pages Deploy
8AIPMAndy/github-pages-deploy-skill
Use when user wants to deploy a static website to GitHub Pages, mentions "一键部署", "GitHub Pages", or needs to publish HTML/web content to a public URL. Triggers on requests like "部署网站", "发布到GitHub", "做个网页并上线".
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.