skill-maintenance

Update documentation guidelines by reviewing architectural changes, new patterns, anti-pattern discoveries, API changes, and security concerns to determine affected skills. Apply minimal-change principles for small, traceable updates to maintain a stable skill tree.

Update your workflow when anti-pattern discoveries, architectural changes, or security concerns affect existing skills. Determine whether updates are required by the guidelines, then perform minimal, well-documented updates to the skill tree.

Maintain a stable skill tree after API changes by enforcing minimal-change principles and clear criteria for adding or deprecating skills. Determine which skills are affected and perform small, traceable updates with clear documentation.

Decide whether to update or deprecate skills by evaluating architectural changes against clear criteria. Determine which skills are affected, whether updates are required by the guidelines, and apply minimal-change principles for stable maintenance.

No, this skill-maintenance workflow does not require any dependencies. It provides structured guidance for updating Claude Code skills after meaningful codebase changes without external components or modules.

Updating skills requires a minimal-change approach to avoid unnecessary churn while ensuring skills stay aligned with evolving patterns and practices. This philosophy emphasizes small, traceable updates and clear documentation for a stable skill tree.