agentsclimarketplace

Session cleanup

Skill smith-horn/product-builder-starter/skills/session-cleanup

11 Claude Code skills for product builders shipping with agentic AI

Install
npx -y skills add smith-horn/product-builder-starter --skill session-cleanup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

End-of-session housekeeping for git repositories. Use when the user asks to 'end of session', 'clean up session', 'session housekeeping', 'clean up branches', 'clean up worktrees', or 'clean up remote branches'.

SKILL.md

3.4 KB, as published. Nobody here has run it

Session Cleanup

Structured end-of-session housekeeping: doc review, branch audit, worktree removal, and remote sync.

Behavioral Classification

Type: Guided Decision

Directive: ASK, THEN EXECUTE

Audits each category and presents findings before taking any destructive action. Deletions always follow an explicit audit phase.

Execution Context Requirements

This skill spawns a general-purpose subagent that performs git operations and file edits.

Foreground execution required: Yes

Required tools: Read, Write, Edit, Bash, Grep, Glob

Fallback: If tools are denied, the subagent returns a checklist of recommended actions for the coordinator to apply manually.

Usage

Invoke at the end of a working session:

/session-cleanup

Or trigger via phrases: "end of session", "clean up branches", "clean up worktrees", "session cleanup"

Out of scope: PR creation/merge (/ship), production deploys, Linear issue updates (/linear), resolving merge conflicts.

Five Phases

  1. Doc Review — CLAUDE.md staleness, MEMORY.md updates, submodule dirty state
  2. Branch Audit — PR status check, unpushed commit detection, squash-merge artifact filtering
  3. Branch Cleanup — Push unreleased content, cherry-pick docs to main, delete merged branches
  4. Worktree Cleanup — Remove stale worktrees via project script or git worktree remove
  5. Final State — Sync main, confirm clean working tree, report summary

Pre-Dispatch Check (REQUIRED — run before spawning agent)

Before launching the cleanup agent, run these two commands via Bash:

git status --porcelain
git branch --list | grep -v "^\* main$"

If both return empty (working tree clean AND only main branch exists locally), cleanup has almost certainly already run this session. Do NOT spawn the agent. Instead, tell the user:

"The repo looks clean already — only main, nothing uncommitted. Cleanup appears to have already run this session. Run it again anyway?"

Only proceed to Dispatch if the user confirms, or if either check returns output (there is real work to do).

Dispatch

Use the Task tool with subagent_type="general-purpose" and pass the full contents
of ./agent-prompt.md as the prompt.

Changelog

v1.2.0 (2026-02)

  • New: Pre-dispatch check — skip agent spawn when repo is already clean
  • New: Two-dot diff gate for unreleased content detection
  • New: --no-verify consent rule — never bypass hooks without explicit user approval
  • New: Abort-gracefully rule — clean state report when user cancels mid-run

v1.1.0 (2026-01)

  • New: Thin dispatcher pattern — full workflow extracted to agent-prompt.md
  • New: Cherry-pick to main for docs-only commits on merged branches
  • New: Worktree cleanup phase using project remove-worktree.sh script
  • New: Squash-merge artifact filtering in branch audit

v1.0.0 (2025-12)

  • Initial release
  • Five-phase workflow: Doc Review, Branch Audit, Branch Cleanup, Worktree Cleanup, Final State
  • Guided decision pattern — audit first, delete only with user approval
  • Remote sync and main branch verification

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.