speckit-cleanup-run

Post-implementation cleanup scans completed feature artifacts for debugging remnants, dead code, and development residue. It reviews changes against your project constitution to identify quality and architecture risks before finalizing.

Severity-based handling resolves small issues with user confirmation, creates follow-up tasks for medium issues, and generates tech-debt analysis for large or constitution-impacting issues. This triage approach ensures safe and tracked code cleanup.

Yes, constitution-first safety guardrails prevent cleanup actions that violate MUST principles by escalating conflicts instead of applying forbidden fixes. This ensures automated code review respects your defined architectural constraints.

A validation loop runs available linters and test runners after applying small fixes to confirm no regressions were introduced. This testing step validates that the cleanup actions maintain codebase stability and integrity.

You generate follow-up tasks for medium-severity code quality risks identified during the artifact review process. This happens when issues are too complex for an immediate fix but require tracked remediation to manage technical debt.

Yes, the validation loop utilizes your available linters and test runners to verify that applied small fixes do not introduce regressions. It integrates with your existing toolchain to validate cleanup actions safely.