reality

Analyze codebases to validate architecture and documentation alignment.

Updated Feb 19, 2026

Search Tags:#architecture #documentation #codebase #drift #analyze #health-score #report-generation

Ready to run

npx skills add https://github.com/fall-out-bug/sdp_lab --skill reality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reality
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/reality
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill reality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift between what is documented and what exists in the codebase can lead to misinformed decisions and failed deployments. This skill analyzes the repository to surface alignment issues and generate a health report.

Core Features & Use Cases

Auto-detect project type and language to tailor analyses.
Compare codebase architecture against references and documentation.
Produce a health score and actionable drift findings to guide remediation.

Quick Start

Invoke the reality skill against a repository to produce a drift report and health score.

Frequently Asked Questions about reality

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

FAQPage Schema

How do I check for architecture drift between my codebase and documentation?▼

To check for architecture drift, you can analyze a codebase to validate architecture and documentation alignment. This process auto-detects the project type and synthesizes a comprehensive drift report highlighting misalignments.

What is codebase documentation drift and how does a health score help?▼

Codebase documentation drift occurs when documented architecture no longer matches the implemented code. A health score quantifies this alignment severity, providing actionable findings to guide remediation and prevent misinformed decisions.

How do I run a quick architecture scan on a large codebase?▼

You can run a quick architecture scan on a large codebase using mode-based scans. By invoking a --quick scan mode, the analysis rapidly auto-detects the project language and generates a baseline drift report.

Can I analyze specific areas of a project for documentation drift?▼

Yes, you can analyze specific areas of a project for documentation drift using the --focus scan mode. This targets particular sections of the codebase, providing a tailored architecture-drift score and structured health report.

What is the best way to generate an architecture health report for a repository?▼

The best way to generate an architecture health report is to run a deep codebase analysis that compares code against references. This approach produces a structured report with a comprehensive health score and actionable drift findings.

When should I run a deep codebase analysis instead of a quick scan?▼

You should run a deep codebase analysis using --deep mode when you need a comprehensive drift report for final validation. Use --quick for fast baseline checks and --focus for targeted architecture-drift scoring.