skill-review

Automate documentation reviews by running systematic audits that check YAML frontmatter validity, version currency, broken links, code example accuracy, and cross-file consistency. This Skill applies audits during major package updates, when last-verified dates exceed 90 days, or before marketplace submission to identify and fix documentation issues automatically.

Automated audits detect YAML syntax errors, outdated tool versions, broken links, stale API methods, code pattern drift, TODO markers, file organization problems, and dependency misalignment. Each issue receives a severity score—CRITICAL, HIGH, MEDIUM, or LOW—enabling prioritized fixes with evidence-based recommendations.

Run audits when major package dependencies release new versions, when last-verified dates exceed 90 days, before submitting to marketplace, or when you suspect version drift between documentation and implementation. Systematic audits ensure code examples remain accurate and production usage patterns align with current APIs.

Yes, the Skill auto-fixes unambiguous issues like correcting YAML syntax, updating stale version references, and removing obsolete code patterns. Manual verification is required for API method correctness and schema consistency; the Skill provides evidence-based recommendations to guide those decisions.

Automated checks verify YAML syntax, tool versions, link validity, and file organization without human review. Manual verification validates API method correctness against official documentation, confirms production usage, and checks schema consistency—tasks requiring domain knowledge that automated tools cannot perform reliably.

The Skill detects version drift through a 9-phase audit covering standards compliance, official documentation alignment, code accuracy verification, and cross-file consistency checks. It identifies mismatches between documented tool versions and actual dependency declarations, then recommends version-bump workflows with fix evidence.