doc-code-review-report

You can verify API documentation against the codebase by providing both to generate an evidence-backed findings report. It checks written claims against real implementation details and runtime contracts, separating confirmed issues from inferences.

Evidence-based code review for design notes is the process of identifying and verifying written claims against the actual codebase. It produces a structured findings report covering logic gaps, contract mismatches, and severity with concrete remediation suggestions.

Yes, you can review PR texts and requirements documents against both frontend and backend codebases. The tool evaluates written materials across both component types to identify inconsistencies, missing behavior, or potential bugs in the implementation.

Generate a code review report by providing a document and running a codebase verification. The output enforces structured findings with documented evidence, explicitly separating confirmed issues from inferred observations and suggesting concrete remediations.

Yes, documentation verification works without external dependencies. The skill operates independently to cross-check user-provided documents against the codebase and requires no additional libraries or external modules to produce its findings report.

The best way to find logic gaps between a design document and a repository is to run a codebase verification. It cross-references written requirements against actual implementation details to produce a comprehensive review highlighting mismatches.