brewcode:teardown
npx machina-cli add skill kochetkov-ma/claude-brewcode/teardown --openclawExecution
Skill arguments received: $ARGUMENTS
If NOT --dry-run: Use AskUserQuestion to confirm before executing:
"This will delete brewcode project files (templates, configs, logs, plans). Task directories are preserved. Proceed?"
EXECUTE using Bash tool — run teardown script:
bash scripts/teardown.sh ARGS_HERE && echo "✅ done" || echo "❌ FAILED"
IMPORTANT: Replace ARGS_HERE with the actual value from "Skill arguments received" above. If empty, omit the argument.
STOP if ❌ — check script path exists and teardown.sh has execute permissions.
Options
| Option | Behavior |
|---|---|
--dry-run | List files to delete without removing them |
| (none) | Full removal after user confirmation |
Preserved
Task directories (.claude/tasks/*_task/) and user rules (.claude/rules/) are always preserved.
Output
# Brewcode Teardown
## Detection
| Field | Value |
|-------|-------|
| Arguments | `{received args or empty}` |
| Mode | `{full or dry-run}` |
## Result
Removed:
✅ .claude/tasks/templates/
✅ .claude/tasks/cfg/
✅ .claude/tasks/logs/
✅ .claude/plans/
✅ .grepai/
✅ .claude/skills/brewcode-review/
Preserved:
⏭️ .claude/tasks/*_task/ (task directories)
⏭️ .claude/rules/ (user rules)
Source
git clone https://github.com/kochetkov-ma/claude-brewcode/blob/main/brewcode/skills/teardown/SKILL.mdView on GitHub Overview
Brewcode teardown removes project files such as templates, configs, and logs. It can run in dry-run mode to preview deletions or prompt for confirmation before full removal. Task directories (.claude/tasks/*_task/) and user rules (.claude/rules/) are preserved.
How This Skill Works
The process delegates deletion to a Bash teardown script. When not in dry-run, it prompts for confirmation and then executes bash scripts/teardown.sh ARGS_HERE; if ARGS_HERE is empty, it runs without additional arguments. It validates that the script path exists and is executable before proceeding.
When to Use It
- Remove templates, configs, and logs from a brewcode project to clean up workspace.
- Run a dry-run (--dry-run) to preview which files would be deleted before actual removal.
- Perform a full cleanup after user confirmation to tidy up a completed or migrated project.
- Prepare a workspace for a new project by pruning legacy brewcode files.
- Ensure task directories (.claude/tasks/*_task/) and user rules (.claude/rules/) stay intact during cleanup.
Quick Start
- Step 1: Decide whether to run in dry-run mode (--dry-run) or perform a full cleanup after confirmation.
- Step 2: Ensure the teardown script path exists and is executable, then substitute ARGS_HERE with your actual arguments if needed (bash scripts/teardown.sh ARGS_HERE).
- Step 3: Run the command and verify the output, confirming preserved directories and successful completion.
Best Practices
- Verify that scripts/teardown.sh exists and is executable before running.
- Always start with a dry-run to confirm what will be deleted.
- Run the command from the project root to ensure correct path resolution.
- Double-check that preserved directories (.claude/tasks/*_task/ and .claude/rules/) will remain untouched.
- Keep a log of deletions and verify there is no unintended data loss.
Example Use Cases
- Cleaning up an old brewcode project before archiving or transferring ownership.
- Freeing disk space after completing a brewcode build by removing temporary templates and logs.
- Tidying a workspace by removing outdated configs and templates while keeping task directories.
- Migrating to a new project structure and pruning legacy brewcode files.
- Presenting a dry-run to stakeholders to show exactly what would be removed before actual cleanup.
