gomtm-refactor

Overview

gomtm-refactor is the single control skill for periodic gomtm convergence work.

Use it after behavior is already correct and the next job is to make the codebase healthier: inventory hotspots, choose a themed cleanup batch, execute the convergence work, verify behavior still holds, and leave a clear record of what was intentionally not changed.

This skill controls the round. Detailed smell rules and stack-specific guidance belong in the reference files, not inline in this main skill.

When to Use

• after a large feature, migration, or implementation batch is already working and needs structural cleanup
• when thin wrappers, single-consumer abstractions, duplicate implementations, semantic duplicate functions, compatibility leftovers, or local fragmentation start accumulating
• when a periodic refactor pass should normalize already-correct code without changing product behavior

Do not use this skill as the starting point for net-new feature design or opportunistic product changes.

Required Workflow