verify-before-documenting

What problem does it solve?

This Skill prevents inaccurate documentation and false claims about codebases by enforcing a strict verification process before any assertions are made. It ensures that documentation is always based on actual code implementation, not assumptions.

Core Features & Use Cases

• Evidence-Based Documentation: Guarantees that all claims about code existence, absence, or state are backed by concrete evidence from the codebase.
• Code Review & Audits: Essential for accurate code reviews, gap analysis, and documentation audits, preventing costly mistakes based on assumptions.
• Use Case: Before documenting that a specific feature is "missing," this skill forces you to search for, read, and verify the actual implementation, ensuring your report is accurate.

Quick Start

Use the verify-before-documenting skill to confirm if the authentication module is implemented by reading the relevant source files.