map-vs-territory

What problem does it solve?

Detects and resolves mismatches between documentation, comments, variable names, and actual runtime behavior so engineers can trust observed results instead of outdated maps. This reduces debugging time, prevents integration failures, and avoids incorrect refactors driven by wrong assumptions.

Core Features & Use Cases

• Reality-first verification: Prescribes probing strategies (logs, runtime inspection, network responses, disk state) to confirm what the system actually does.
• Safety-aware protocol: Includes a pre-flight checklist to avoid running unsafe or irreversible commands in production contexts.
• Self-improvement & audit logging: Provides patterns and optional correction logs to capture recurring documentation drift and guide systemic fixes.
• Use Cases: Debugging API contract drift, validating third-party integrations, investigating legacy code where comments no longer match implementation.

Quick Start

Use the map-vs-territory skill to verify whether the API response and runtime types match the documentation and log any systemic discrepancies.