phase-cleanup

Refactor code and update documentation after parallel development phases complete.

18|5|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/mvillmow/ml-odyssey --skill phase-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-cleanup
Source: https://github.com/mvillmow/ml-odyssey/tree/main/.claude/skills/phase-cleanup
Command: npx skills add https://github.com/mvillmow/ml-odyssey --skill phase-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? This Skill coordinates the final cleanup phase of development, addressing technical debt, refactoring code, and ensuring documentation and quality checks are complete before merging. It automates the final polish, reducing manual oversight.

Core Features & Use Cases:

  • Technical Debt Resolution: Identifies and helps remove duplication, improve naming, and simplify complex code, enhancing maintainability.
  • Documentation Update: Ensures all documentation (READMEs, docstrings, ADRs) is accurate and complete, improving project clarity.
  • Use Case: After completing a feature, use this skill to run a comprehensive cleanup. It will help you refactor complex functions, remove dead code, update documentation, and ensure all quality checks pass, preparing your code for a smooth merge.

Quick Start: Use the phase-cleanup skill to run the cleanup phase for the current project, focusing on refactoring and documentation.

Frequently Asked Questions about phase-cleanup

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

FAQPage Schema
How do I refactor code and remove technical debt before merging?

Refactoring code to remove technical debt involves identifying duplication, improving naming, simplifying complex logic, and removing dead code. Phase-cleanup automates this final polish by consolidating outputs, fixing quality issues, and preparing code for merge after parallel development phases complete.

What should I do to ensure documentation matches my implementation?

Documentation updates ensure READMEs, docstrings, and architecture decision records stay accurate and complete. Phase-cleanup verifies all documentation aligns with the final implementation, improving project clarity and reducing confusion for future maintainers.

When do I run code cleanup in my development workflow?

Code cleanup runs during the final phase after Test, Implementation, and Package phases complete. This timing lets you consolidate outputs from parallel work, address accumulated quality issues, and satisfy formatting and linting requirements before merge.

Can phase-cleanup help remove TODO and FIXME comments automatically?

Phase-cleanup addresses cleanup requirements including removal of TODOs and FIXMEs as part of preparing code for merge. It scans for these markers and helps resolve or document outstanding work items before final integration.

How do I ensure zero warnings and full test coverage before merging?

Phase-cleanup validates that formatting, linting, test coverage, and zero-warning requirements are met. It performs comprehensive quality checks across your codebase to confirm all standards are satisfied before code reaches merge readiness.