grey-haven-documentation-alignment

Code-documentation alignment verification automatically compares function signatures, types, behaviors, errors, and examples between your implementation and docs to identify mismatches. This Skill validates across all three elements—references, examples, and templates—and scores alignment on a 0–100 scale, surfacing discrepancies like signature drift, missing parameters, or broken examples so you can fix them before release.

Yes. This Skill is designed for onboarding workflows to automatically verify that new developers see accurate, aligned documentation. It runs the six-phase workflow—discovery, extraction, analysis, classification, fix generation, and validation—on modules or components to confirm all function signatures and behaviors match docs, reducing onboarding time by up to 40%.

This Skill works across languages and frameworks by validating code implementations against their documentation at the signature, type, behavior, error, and example level. It applies to modules or components regardless of the underlying tech stack, making it suitable for polyglot projects and teams.

Run this Skill after code changes, before pre-release checks, during onboarding, or whenever you need to catch documentation drift. The six-phase workflow generates an alignment score and actionable fixes, making it easy to integrate into CI/CD pipelines or manual review gates to prevent signature drift and broken examples from reaching users.

The Skill outputs an alignment score (95–100: Perfect, 0–59: Failing), a detailed discrepancy report identifying which elements are misaligned, and actionable fixes you can apply to either code or documentation to restore alignment.

This Skill applies to modules or components of any size. It discovers, extracts, and analyzes code-docs pairs systematically, then classifies and generates fixes—scaling the validation workflow to match your project's scope.