cleanup

Automates removal of deleted component code from spec-driven workflows using bead IDs and safety checks.

4|Updated Feb 24, 2026

Search Tags:#task automation #spec-driven development #code cleanup #codebase maintenance #bead management

Ready to run

npx skills add https://github.com/dmitriyb/spexmachina --skill cleanup-dmitriyb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/dmitriyb/spexmachina/tree/main/skills/cleanup
Command: npx skills add https://github.com/dmitriyb/spexmachina --skill cleanup-dmitriyb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of removing code for components that have been deleted from the spec, ensuring clean and up-to-date codebases.

Core Features & Use Cases

Automated Code Removal: Removes implementation and test files associated with deleted components.
Bead Tracking: Utilizes beads for tracking and managing tasks within the spec.
Safety Checks: Performs multiple checks to ensure correct execution and prevent mistakes.

Quick Start

To remove code for a component, use the cleanup skill with the bead ID as the argument: cleanup <bead-id>

Frequently Asked Questions about cleanup

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

FAQPage Schema

How do I automate code cleanup for deleted components in a spec-driven workflow?▼

Automated code cleanup removes implementation and test files for deleted components. It uses a bead ID argument to trigger the removal process within a spec-driven workflow. This ensures your codebase stays clean and up-to-date without manual file deletion.

What are beads in spec-driven development and how do they manage code removal tasks?▼

Beads are tracking elements used for task management within a spec. The cleanup skill processes a specific bead ID to identify and remove the associated deleted component files. This mechanism ensures precise tracking of what needs to be removed from the codebase.

How do I safely remove implementation and test files without breaking dependencies?▼

Safe code removal is achieved through built-in safety checks that validate dependencies before executing any file deletion. The skill performs multiple checks to ensure correct execution and prevent mistakes, protecting your codebase from broken references.

Can I use automated codebase maintenance to delete files for components removed from my spec?▼

Yes, automated codebase maintenance specifically targets components deleted from your spec. By passing the bead ID to the cleanup process, the skill removes the implementation and test files associated with that deleted component automatically.

What limitations or precautions should I consider before automating code removal?▼

Automated code removal relies on accurate bead tracking and spec definitions to function correctly. You must ensure the provided bead ID accurately represents the deleted component, as the safety checks validate dependencies based on this tracking data to prevent unintended deletions.