component-refactor

Run the audit mode with a language argument, such as `cpp audit`. It first executes the vitest integration guardrails (audit-completeness, audit-component-locality, audit-orphan-implementations), then manually scans confidence-level compliance and i18n label style, which the guardrails do not cover.

Use fix mode with the component or module name, such as `cpp fix vector`. The Skill diagnoses missing paths, derives lifters from existing generators or vice versa, generates the artifacts, and verifies each fix with `npx tsc --noEmit` and `npm test` before moving on.

Migrate when the lifter is pure field mapping (L1), needs a simple transform or operator dispatch (L2), or has multi-condition logic under 20 lines (L3 composite). Lifters with cross-node state or deep nested logic are classified unmovable and stay hand-written.

No. Most checks—five-path completeness, dual registration, dead concepts, encapsulation, naming—are already covered by mechanized vitest guardrails with baselines. The Skill only manually scans confidence-level compliance and i18n label style, which require judgment rather than counting.

Dead concepts (0/6 completeness) are evaluated for retention value: exploration reports, dependency references, or topic tree membership mean they get fixed instead. Only concepts with no value and no references are purged by deleting the entire capsule folder.

The Skill is designed to never break tests: it repairs one component at a time, runs `npx tsc --noEmit` and `npm test` after every change, and stops immediately if any step in the full pipeline fails, reporting the failure instead of continuing.