phase-cleanup

Name: phase-cleanup
Availability: InStock
Author: HomericIntelligence

Refactor and finalize code after parallel development phases.

18|5|Updated Nov 3, 2025

Search Tags:#code quality #testing #code review #refactoring #CI/CD #cleanup

Ready to run

npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill phase-cleanup-homericintelligence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phase-cleanup
Source: https://github.com/HomericIntelligence/ProjectOdyssey/tree/main/.claude/skills/phase-cleanup
Command: npx skills add https://github.com/HomericIntelligence/ProjectOdyssey --skill phase-cleanup-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires just, pixi, and includes references (resource) components.

What problem does it solve?

This Skill addresses the need to consolidate, refactor, and ensure high code quality after parallel development phases, preparing code for integration.

Core Features & Use Cases

Technical Debt Reduction: Identifies and resolves TODOs, FIXMEs, and code duplication.
Quality Assurance: Enforces formatting, linting, testing, and a zero-warnings policy.
Use Case: After feature development and testing, this skill is invoked to clean up the codebase, ensuring it adheres to project standards and is ready for peer review and merging.

Quick Start

Use the phase-cleanup skill to run all quality checks and format the code.

Frequently Asked Questions about phase-cleanup

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

FAQPage Schema

How do I resolve technical debt and code duplication before merging a new feature?▼

To reduce technical debt before merging, you need to refactor the codebase by identifying and eliminating TODOs, FIXMEs, and code duplication while strictly enforcing KISS, DRY, and SOLID principles to ensure high code quality.

What is the best way to enforce a zero-warnings policy during code review?▼

The best way to enforce a zero-warnings policy during code review is to apply strict quality assurance checks that automate formatting, linting, and testing across the codebase immediately before the final merge.

Do I need just and pixi to automate code cleanup and formatting?▼

Yes, you need just and pixi installed as dependencies to automate the final code cleanup phase, which runs quality checks and formats the code to prepare it for integration into the main branch.

When should I refactor code after parallel development phases?▼

You should refactor code after parallel development phases conclude and testing is complete, serving as the final stage of the development workflow to consolidate features and prepare the code for peer review and merging.

Can I use this refactoring approach to enforce SOLID principles in CI/CD pipelines?▼

Yes, you can integrate this refactoring approach into CI/CD pipelines to automatically enforce SOLID principles, ensuring all code adheres to project standards and passes formatting and testing checks before merging.