naming-refactor

Topics in the source

• Naming Refactor
• Contract
• Coverage Ledger
• Ground the Refactor
• Build the Rename Map
• Acquire the Implementation Scope
• Execute in Verified Waves
• Final Verification and Report

If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool. Make every name in the current repository communicate one coherent domain model, regardless of refactor cost. Cover the complete current Git repository. Do not narrow the run to selected files or stop after a candidate cap. Preserve features, runtime behavior, side effects, performance-sensitive characteristics, and externally consumed contracts. Large diffs, path moves, and repository-controlled interface migrations are allowed. Treat an exported surface as repository-controlled only when every consumer is in scope and can migrate atomically. Preserve other API names, CLI flags, environment variables, configuration keys, wire fields, routes, database names, and import paths unless the user explicitly authorizes a breaking migration. Fix a bug discovered during the refactor only when the defect and intended behavior are clear and a regression check can prove the fix. Keep bug fixes in a distinct change wave and report them separately. Preserve pre-existing work. Local edits, file moves, directory restructuring

This is an excerpt. Refer to the complete source and its current requirements.