When should I invoke the phase-cleanup skill?

Invoke this skill after the Test, Implementation, and Package phases are complete, but before you seek final PR approval or attempt to merge code.

What is the Zero-Warnings Policy enforced by this skill?

It ensures that the code compiles without any warnings in the build log, treating warnings as errors to maintain high code quality.

What is the primary purpose of the Phase-Cleanup skill?

It is used as a final quality gate to refactor code, remove technical debt, and ensure the project meets all quality standards before merging into the main branch.

Does this skill work with any programming language?

While the principles are universal, this specific skill is optimized for the Mojo programming language and the Project Odyssey framework workflows.

Phase-Cleanup: Code Refactoring & Polishing

Name: Phase-Cleanup: Code Refactoring & Polishing
Author: HomericIntelligence

byHomericIntelligence

•

Productividad y Flujo de Trabajo

Refactors and finalizes code after parallel development phases to address technical debt and ensure merge readiness.

The Phase-Cleanup skill is designed for the final stage of the Project Odyssey workflow, acting as a quality gate before code is merged into the main branch. It automates the process of addressing technical debt by scanning for TODOs, enforcing Mojo-specific formatting, and applying core architectural principles like KISS, DRY, and SOLID. By consolidating outputs from parallel test and implementation phases, this skill ensures that codebase remains clean, documented, and compliant with a strict zero-warnings policy, significantly reducing the burden of manual code reviews.

Características Principales

01Comprehensive pre-merge quality checklists and verification scripts

0214 GitHub stars

03Automated technical debt scanning for TODO, FIXME, and HACK comments

04Architectural refactoring based on KISS, DRY, and SOLID principles

05Mojo-specific code formatting and linting via pixi and mojo tools

06Zero-warnings policy enforcement during the build process

Casos de Uso

01Consolidating parallel development outputs into a cohesive, simplified codebase

02Systematic removal of dead code and standardization of error handling across modules

03Finalizing feature branches to ensure they are production-ready before PR submission

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add homericintelligence/projectodyssey phase-cleanup

For use in Claude.ai and ChatGPT

Download Skill