Repo Cleanup

Overview

Establish a safe, repeatable cleanup workflow for code, dependencies, docs, tests, and sprint artifacts. Minimize risk by validating usage, archiving before deletion, and verifying with tests.

When to Use

• Repository bloat (generated artifacts, caches, unused files)
• Dead code or unused dependencies suspected
• Docs drifted from actual behavior
• Tests are brittle, redundant, or mislocated
• Sprint closure needs structured archiving

Avoid when:

• Active incident response is ongoing
• The target area lacks owners or rollback coverage

Quick Reference