reality-check

Validate documentation against code and output a mismatch report.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/fall-out-bug/sdp_lab --skill reality-check-fall-out-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reality-check
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/reality-check
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill reality-check-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that documentation matches the actual code before making changes.

Core Features & Use Cases

  • Quick cross-check of documentation against code to ensure alignment.
  • Useful during feature updates, API changes, or reviews to catch mismatches early.
  • Example: verify that a README section describing a function matches the actual behavior implemented.

Quick Start

Run a quick validation pass to compare docs with the target module and report any mismatches.

Frequently Asked Questions about reality-check

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

FAQPage Schema
How do I validate that my documentation matches the actual code?

To validate documentation against code, run a conformance check that compares doc statements to code behavior and outputs a mismatch report. This catches alignment issues before making feature updates or API changes.

What is a docs-vs-code reality check and when do I need it?

A docs-vs-code reality check is a conformance validation that compares documentation statements to actual code behavior. You need it during feature updates, API changes, and cross-module edits to ensure alignment.

How do I check if a README section matches the actual function behavior implemented?

To check if a README matches function behavior, run a quick validation pass comparing the documentation to the target module. This cross-check reports any mismatches between described and implemented behavior.

Can I use this for code review conformance checks during API changes?

Yes, you can use this for code review conformance checks during API changes. It validates that documentation matches actual code behavior and reports mismatches, ensuring alignment before finalizing updates.

What is the best way to catch documentation mismatches early in feature updates?

The best way to catch mismatches early is running a quick cross-check of documentation against code. This conformance check compares doc statements to code behavior and outputs a mismatch report for review.