documentation-alignment

6-phase verification system ensuring code matches documentation with automated alignment scoring (signature, type, behavior, error, example checks). Reduces onboarding friction 40%. Use when verifying code-docs alignment, onboarding developers, after code changes, pre-release documentation checks, or when user mentions 'docs out of sync', 'documentation verification', 'code-docs alignment', 'docs accuracy', 'documentation drift', or 'verify documentation'.

Jump to install Review files

Repository: greyhaven-ai/claude-code-config
Last source activity: April 17, 2026 at 23:11
Detected SKILL.md language: English
Stars: 29
Forks: 5

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/greyhaven-ai/claude-code-config/tree/main/grey-haven-plugins/core/skills/documentation-alignment.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/greyhaven-ai/claude-code-config --skill documentation-alignment

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

name: documentation-alignment
description: 6-phase verification system ensuring code matches documentation with automated alignment scoring (signature, type, behavior, error, example checks). Reduces onboarding friction 40%. Use when verifying code-docs alignment, onboarding developers, after code changes, pre-release documentation checks, or when user mentions 'docs out of sync', 'documentation verification', 'code-docs alignment', 'docs accuracy', 'documentation drift', or 'verify documentation'.
skills: ["code-style"]
allowed-tools: ["Read","Grep","Glob","TodoWrite"]

# Documentation Alignment Skill 6-phase verification ensuring code implementations match their documentation with automated alignment scoring. ## Description Systematic verification of code-documentation alignment through discovery, extraction, analysis, classification, fix generation, and validation. ## What's Included - **Examples**: Function signature mismatches, parameter changes, type updates - **Reference**: 6-phase process, alignment scoring formula - **Templates**: Alignment report structures - **Checklists**: 101-point verification checklist ## Alignment Scoring Score = (Signature×30% + Type×25% + Behavior×20% + Error×15% + Example×10%) - 95-100: Perfect - 80-94: Good - 60-79: Poor - 0-59: Failing ## Use When - Onboarding new developers (reduces friction 40%) - After code changes - Pre-release documentation verification ## Related Agents - `documentation-alignment-verifier` **Skill Version**: 1.0

View on GitHub

Back to search Back to installation

code-quality-analysis

Multi-mode code quality analysis covering security reviews (OWASP Top 10), clarity refactoring (readability rules), synthesis analysis (cross-file issues), and DDD/DRY lenses (flags mechanical naming, primitive obsession, domain rules leaking into infrastructure, and premature abstractions via the three-occurrences-same-concept rule). Supports team-mode parallel analysis when invoked from quality-pipeline. Use when reviewing code for security vulnerabilities, improving code readability, conducting quality audits, pre-deployment checks, or when user mentions 'code quality', 'code review', 'security review', 'refactoring', 'code smell', 'OWASP', 'code clarity', 'primitive obsession', 'value object', 'ubiquitous language', 'DRY', 'premature abstraction', or 'quality audit'.

2026-04-19

performance-optimization

Comprehensive performance analysis and optimization for algorithms (O(n²)→O(n)), databases (N+1 queries, indexes), React (memoization, virtual lists), bundles (code splitting), API caching, and memory leaks. 85%+ improvement rate. Use when application is slow, response times exceed SLA, high CPU/memory usage, performance budgets needed, or when user mentions 'performance', 'slow', 'optimization', 'bottleneck', 'speed up', 'latency', 'memory leak', or 'performance tuning'.

2026-04-19

api-design-standards

Design RESTful APIs following Grey Haven standards - FastAPI routes, Pydantic schemas, HTTP status codes, pagination, filtering, error responses, OpenAPI docs, and multi-tenant patterns. Use when creating API endpoints, designing REST resources, implementing server functions, configuring FastAPI, writing Pydantic schemas, setting up error handling, implementing pagination, or when user mentions 'API', 'endpoint', 'REST', 'FastAPI', 'Pydantic', 'server function', 'OpenAPI', 'pagination', 'validation', 'error handling', 'rate limiting', 'CORS', or 'authentication'.

2026-04-19

View all from this repository

documentation-alignment

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository