code-truth-validation

Validate documentation statements against actual code signatures and file references.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill code-truth-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-truth-validation
Source: https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit/tree/main/skills/code-truth-validation
Command: npx skills add https://github.com/BrunoSantanaDeveloper/flyeelab-agent-kit --skill code-truth-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that documentation statements reflect the actual code, preventing inconsistencies between docs and implementation in integrations, gateways, enums, and referenced files.

Core Features & Use Cases

  • Enforces live-code truth checks before documentation is published, ensuring references exist and signatures match.
  • Detects and surfaces divergences between current code state and documented claims, enabling fast remediation.
  • Supports cross-scope validation across integrations, components, and configuration references to improve overall documentation quality.

Quick Start

Before saving any technical doc, run the code-truth validation to detect and correct discrepancies.

Frequently Asked Questions about code-truth-validation

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

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

To validate documentation against a codebase, run automated truth checks to ensure referenced files exist and function signatures match before publishing docs.

What is code-truth validation for technical documentation?

Code-truth validation is the process of verifying that documentation statements match actual code, preventing inconsistencies across integrations, gateways, and API components.

How do I detect divergences between documented APIs and current code?

Detect divergences between documented APIs and code by running validation checks that compare documented claims against the current code state, recording mismatches as technical debt.

Can I verify configuration references and enums across my codebase?

Yes, you can verify configuration references and enums across a codebase by applying cross-scope validation to ensure every referenced file exists and matches its implementation.

When should I run documentation consistency checks in my workflow?

Run documentation consistency checks before saving or publishing any technical doc to detect discrepancies early and correct divergences between the documentation and implementation.