code-cleanup

To remove unused imports and redundant functions from generated code, you can apply an automated cleanup process that systematically questions each component's purpose and eliminates anything unnecessary. The Skill audits every function and import to delete redundant code.

To ensure code aligns with project goals, cross-reference each component against a GOAL.md file to verify relevance. The Skill validates that every function, class, and import contributes directly to the defined outcome.

The best way to refactor for maintainability is to systematically question each function, eliminate unused code, and apply concise naming guidelines. This process simplifies complex sections and enforces short, descriptive identifiers.

To keep track of code modifications during refactoring, log all changes in a project management file. The Skill records every modification inside .sgai/PROJECT_MANAGEMENT.md to ensure full traceability of removed or updated components.

Yes, the cleanup process requires a GOAL.md file to validate that each code element contributes to the defined outcome. It cross-references every function, class, and import against this document to verify relevance before removing or refactoring.