reversa-depth-inspection

Inspects a feature across specs, code, tests, and data with parallel specialized lenses to register confirmed bugs.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-depth-inspection-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-depth-inspection
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-depth-inspection
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-depth-inspection-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature keeps breaking, fixing one bug at a time misses systemic defects. This Skill performs a deep, read-only inspection of an entire feature—mapping its specs, code, tests, and data—then sweeps it with specialized lenses to surface every confirmed defect as a tracked bug. ## Core Features & Use Cases - Feature Mapping: Builds a spec→code→tests→data map of the target feature before scanning, including existing registered bugs to avoid rediscovery. - Parallel Specialized Lenses: Runs six mandatory lenses (spec conformance, data flow, contracts/integrations, error states, test coverage, concurrency) plus conditional lenses for security, performance, config drift, and observability. - Centralized Bug Registration: Deduplicates findings, confirms only observable deviations, and registers accepted bugs serially in _reversa_bugs/<context>/bugs/ with full traceability, plus a consolidated inspection report. - Use Case: A checkout feature keeps failing in production. Run this Skill to map the feature, sweep it with all lenses, and convert confirmed findings into tracked bugs with a report showing suspicious clusters. ## Quick Start Ask the agent to run a deep inspection on the feature that keeps causing problems, for example: "Run a depth inspection on the payment feature and register every confirmed bug."

Frequently Asked Questions about reversa-depth-inspection

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

FAQPage Schema
How do I find all bugs in a feature that keeps breaking?▼

Run a depth inspection that first maps the feature's specs, code, tests, and data, then sweeps it with specialized lenses covering conformance, data flow, contracts, error states, test coverage, and concurrency. Confirmed findings are registered as tracked bugs with evidence.

What does a spec-to-code conformance inspection check?▼

It compares the implemented behavior against the effective spec (original plus active amendments) to find divergences. Each finding includes confidence level, file-and-line evidence, suspected severity, and signals like data corruption or security risk.

Does this inspection modify or fix my code?▼

No. The inspection is strictly read-only and diagnostic. It writes only new bug records and reports inside the _reversa_bugs directory and never edits, refactors, or deletes existing project files.

How are duplicate findings across lenses handled?▼

After all lenses finish, findings are merged and deduplicated against each other and against already-registered bugs using matching specs, files, and symptoms. Only findings with observable deviation or complete causal proof are promoted to bugs.

When should I use a depth inspection instead of fixing a single bug?▼

Use it when a feature repeatedly produces bugs, suggesting structural causes. A single bug fix addresses one symptom, while the inspection sweeps the whole feature and clusters findings to reveal common root causes.