skills.rest
cowwoc
cowwocCOMMUNITY
Explore all skills by this author →
GitHub

pre-presentation-cleanup

Remove agent worktrees, delete subagent branches, and squash commits before review.

4|Updated Sep 25, 2025
Search Tags:#git#commit#cleanup#archival#presentation
One-click install
npx skills add https://github.com/cowwoc/styler --skill pre-presentation-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-presentation-cleanup
Source: https://github.com/cowwoc/styler/tree/main/.claude/skills/pre-presentation-cleanup
Command: npx skills add https://github.com/cowwoc/styler --skill pre-presentation-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure mandatory cleanup before presenting changes for user approval, producing clean commits and a tidy project state.

Core Features & Use Cases

  • Remove agent worktrees and agent branches.
  • Update archival files (todo.md, changelog.md) to reflect completion.
  • Squash commits into two coherent commits (config + implementation) when needed.
  • Verify cleanup state and readiness for presentation.

Quick Start

TASK_NAME="implement-formatter-api" /workspace/main/.claude/scripts/pre-presentation-cleanup.sh
--task "$TASK_NAME"

Frequently Asked Questions about pre-presentation-cleanup

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

FAQPage Schema
How do I clean up commits before presenting changes for user review?▼

Pre-presentation cleanup removes agent worktrees, deletes temporary branches, updates archival files like todo.md and changelog.md, and squashes commits into two coherent commits (config and implementation) to produce a clean, presentation-ready state.

What does pre-presentation cleanup do with Git branches and worktrees?▼

It eliminates stale agent worktrees and deletes subagent branches, ensuring no temporary development artifacts remain in the repository before user-facing review.

How do I organize commits into a two-commit structure?▼

The cleanup process squashes commits into two logical commits—one for configuration changes and one for implementation—making the history clear and reviewable.

When should I run commit cleanup in my Git workflow?▼

Run cleanup when a task reaches AWAITING_USER_APPROVAL status, just before presenting changes for final approval, or in workflows requiring archival updates with a structured two-commit format.

Does pre-presentation cleanup verify the repository state before review?▼

Yes, it verifies cleanup state and readiness for presentation, confirming that worktrees are removed, branches are deleted, and archival files are updated before changes are presented.

Related Skills

Explore More Software Engineering Skills→
voidreadervoidreader

finalize-feature

Analyzes repository changes and creates a finalized commit without pushing.

Community
Advanced
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
7loro7loro
1

git-master

Organize multi-file Git changes into atomic commits with rebase and squash workflows.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-reflog

Recover lost Git commits and branches using reflog history.

Community
Intermediate