manage-skills

Verification skill drift is detected by analyzing session file changes, parsing SKILL.md frontmatter, and executing glob and grep validations to find uncovered files and outdated references. This process identifies gaps between repository changes and registered verify-* skills.

Synchronizing verification registries requires a 3-way sync mechanism that enforces consistent updates across manage-skills, verify-implementation, and project CLAUDE.md. The process validates Related Files patterns and detection commands to ensure all registries reflect current repository state.

Coverage mapping extracts Related Files patterns and detection commands from registered verify-* SKILL.md files, then matches them against changed files. This matching process identifies UNCOVERED files, outdated references, and missing checks caused by session file modifications.

Automated proposals suggest agent delegation, existing-skill updates, or new verify-* skill creation when code, configuration, or tests are modified. These proposals are generated during PR review, post-implementation checks, and periodic audits based on detected coverage gaps.

Periodic audits should run during PR review, post-implementation checks, and whenever code, configuration, or tests are modified. These audits parse SKILL.md frontmatter and Related Files tables, executing glob and grep validations against the repository tree to catch drift.

Changed files remain uncovered when session file changes outpace registered verification skills. The tool groups changed files by top-level directories and cross-references them against extracted Related Files patterns to pinpoint exactly which areas lack verification coverage.