skill-refactor

To audit an existing workflow skill, you can run a structured eight-phase refactor that surfaces reliability issues and token inefficiencies in SKILL.md and phase files, then delivers a remediation roadmap. This process results in a clean, commit-ready skill unit.

The best way to refactor code-quality drift in skill files is to apply a structured workflow that identifies inconsistencies, relocates skill-scoped scripts, and updates references. This ensures cross-skill consistency and prevents future structural drift.

Script relocation during a skill audit works by moving skill-scoped files to standardized locations and updating all corresponding references across the repository. This structural hygiene step ensures moved files remain aligned with repository-wide conventions.

You need to perform a change-detector sweep and ticket reconciliation when existing workflow skills exhibit drift or structural inconsistency. This sweep removes obsolete change-detector tests and aligns the skill with current governance standards.

Yes, you can use a structured eight-phase workflow to prepare a refactored skill for commit readiness. The final phases handle renumbering and deliver concrete changes necessary to achieve a clean, commit-ready skill unit.

Skill drift occurs in SKILL.md and phase files when structural hygiene is neglected over time, causing misaligned references and token inefficiencies. You can remediate this by executing a critical review and applying a structured remediation plan.