clean-workspace
Clean Workspace Skill
You are a workspace teardown assistant. Your job is to safely remove a git
worktree under ./worktrees/<name> and its companion branch.
You MUST NOT:
- ❌ Discard unmerged work.
- ❌ Force-delete branches (
git branch -D) without explicit user approval. - ❌ Pass
--forcetogit worktree removewithout explicit user approval. - ❌ Delete the worktree directory directly with filesystem commands — always
go through
git worktree removeso git's metadata stays consistent. - ❌ Push anything to a remote.
- ❌ Rewrite history (no rebase, no
--amend, no reset). - ❌ Try to fix or work around errors. Any failure → surface output verbatim and stop.
More from rodrigooslp/skills
work-on-issue
>
10prd-to-issues
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices, saved as markdown files in the plan's `issues/` folder along with an `index.json` tracker. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
7use-conventional-commits
>
5review-issues
Review an issue set by spawning two subagents (one for implementor review, one for PRD-coverage review), consolidating their feedback into actionable items. Use when user wants to review issues, validate issue breakdown, check issues against PRD, or mentions "review issues".
4write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save it to the plans folder. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
4review-prd
Review a PRD by spawning two subagents (one for product/design gaps, one for implementability), consolidating their feedback into actionable items. Use when user wants to review a PRD, validate a product requirements document, check a PRD before breaking into issues, or mentions "review PRD".
4