code-review-documentation-checker

Identify code changes requiring documentation updates during code review.

21|8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/speednet-software/speedwave --skill code-review-documentation-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-documentation-checker
Source: https://github.com/speednet-software/speedwave/tree/main/.claude/skills/code-review-documentation-checker
Command: npx skills add https://github.com/speednet-software/speedwave --skill code-review-documentation-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify when code changes require documentation updates during code review to prevent drift between code and docs.

Core Features & Use Cases

  • Cross-check changes against public API docs, in-line comments, and configuration references.
  • Flag missing or outdated documentation and generate a remediation checklist.
  • Provide traceability by linking diffs to related documents and sections.
  • Use Case: when a new API endpoint is added, review detects need to update API docs and examples.

Quick Start

During a code review, run the documentation checker to surface required updates and ensure alignment between code changes and docs.

Frequently Asked Questions about code-review-documentation-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if code changes require documentation updates during code review?

To check if code changes require documentation updates during code review, run the documentation checker to cross-reference diffs against public APIs, configurations, and inline comments, surfacing required updates to prevent drift.

What is documentation drift and how do I prevent it?

Documentation drift occurs when code changes outpace doc updates. Prevent drift by applying the documentation checker across public APIs, configurations, and inline comments to ensure synchronization and cross-reference integrity during review.

How do I detect missing or outdated API docs when a new endpoint is added?

Detect missing or outdated API docs by running the documentation checker during review; it flags required updates for new endpoints and generates a remediation checklist linking diffs to related documents.

Can I trace code diffs to related documentation sections automatically?

Yes, you can trace code diffs to related documentation sections automatically; the checker provides traceability by linking diffs to related documents and sections to ensure accuracy and completeness.

Does the documentation checker validate cross-reference integrity between code and docs?

Yes, the documentation checker validates cross-reference integrity between code and docs by applying checks across public APIs, configurations, and inline comments to ensure synchronization and completeness.

What's the best way to generate a remediation checklist for outdated inline comments?

The best way to generate a remediation checklist for outdated inline comments is to run the documentation checker during code review, which flags missing or outdated documentation and outputs a linked checklist.