brewcode:teardown

Remove brewcode temporary and configuration files while preserving task directories.

30|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-teardown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brewcode:teardown
Source: https://github.com/kochetkov-ma/claude-brewcode/tree/main/brewcode/skills/teardown
Command: npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-teardown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes temporary and configuration files generated by the brewcode setup process, helping to declutter your project environment without deleting your actual work.

Core Features & Use Cases

  • Project Cleanup: Removes setup templates, configuration files, logs, plans, and semantic search indexes.
  • Preserves Work: Ensures that task directories and their content, along with user rules, remain untouched.
  • Use Case: After completing a series of development tasks managed by brewcode, you can use this skill to reset the project's temporary state, preparing it for a new set of tasks or a clean slate.

Quick Start

Run the teardown skill to clean up all brewcode project files.

Frequently Asked Questions about brewcode:teardown

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

FAQPage Schema
How do I clean up temporary brewcode project files?

You clean up temporary brewcode project files by running the teardown skill, a bash script that removes setup templates, logs, plans, and indexes to declutter your environment.

Does project cleanup with teardown delete my task directories?

Project cleanup with teardown does not delete your task directories. It specifically preserves user-created task content and custom rules while removing temporary configuration files.

What files are removed when resetting a brewcode development environment?

Resetting a brewcode development environment removes setup templates, configuration files, logs, plans, and semantic search indexes, while safely preserving your actual work and custom rules.

When should I use a teardown script for project management cleanup?

Use a teardown script for project management cleanup after completing development tasks to reset the project's temporary state, preparing a clean slate for a new set of tasks.

Can I safely remove brewcode logs and indexes without losing custom rules?

You can safely remove brewcode logs and indexes without losing custom rules because the teardown script specifically targets temporary files for deletion while explicitly preserving your custom configurations.