work-closeout

Coordinates GitHub plan cleanup, git worktree hygiene, and safe-to-exit closeout verdicts.

5|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill work-closeout-cbusillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-closeout
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/work-closeout
Command: npx skills add https://github.com/cbusillo/codex-skills --skill work-closeout-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Ending a coding session cleanly is error-prone: stale plans linger, worktrees pile up, transient artifacts confuse the next session, and nobody can say whether it is actually safe to exit. This Skill standardizes workstream closeout so unfinished work is parked durably and finished work is verified, cleaned, and summarized. ## Core Features & Use Cases - Safe-to-exit verdicts: Produces a yes/conditional/no verdict backed by evidence, including a mandatory Love Gate section with explicit Love: and Do not love: entries. - Git and worktree hygiene: Applies pinned-commit fast-forward rules, runtime-bound checkout reconciliation, and bounded untracked-only exceptions without destructive commands. - GitHub plan and issue reconciliation: Updates plan issues, blocker graphs, labels, and Project state, and migrates or removes stale local plans and handoff files. - Read-only cleanup inventory: Ships a helper script that reports scoped cleanup evidence without authorizing or performing deletion. - Use Case: After merging a PR, ask the agent to wrap up: it verifies post-merge state, fast-forwards the default checkout, removes the merged task worktree, updates the owning issue, and reports a final safe-to-exit verdict. ## Quick Start Ask the agent to wrap up the current task and tell you whether it is safe to exit, including what was cleaned up and what remains.

Frequently Asked Questions about work-closeout

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

FAQPage Schema
How do I safely close out a coding session with an AI agent?

Invoke the closeout workflow, which inspects git status, worktrees, GitHub issues and plans, then reports what changed, what remains, and a safe-to-exit verdict of yes, conditional, or no with evidence.

What is the Love Gate in closeout answers?

The Love Gate is a required final section where the agent states what it loves about the result and what it does not love, such as compromises or remaining technical debt. It uses explicit `Love:` and `Do not love:` entries before the safe-to-exit verdict.

Does the cleanup script delete files automatically?

No. The repo_cleanup.py helper is read-only: it reports scoped cleanup inventory, revalidates private snapshots, and verifies post-action state. Deletion decisions and mutations remain with the agent under the shared cleanup policy.

When should I use repo-readiness instead of work-closeout?

Use repo-readiness when the question is whether checks pass or a PR can ship. Use work-closeout for final hygiene, cleanup, and parking state; when both apply, run repo-readiness first and consume its handoff.

Can closeout fast-forward a dirty git checkout?

Only under a bounded exception: the user must explicitly request it, the checkout must be non-runtime-bound on the default branch, and dirt must be untracked non-ignored files only. All other dirty, diverged, or ambiguous states are report-only.