reversa-depth-inspection

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

1.5k|405|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-depth-inspection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-depth-inspection
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-depth-inspection
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-depth-inspection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a feature keeps breaking, fixing one bug at a time misses the systemic issues. This Skill performs a deep, read-only inspection of an entire feature—mapping its specs, code, tests, and data—then sweeps it with specialized diagnostic lenses so every confirmed defect becomes a registered, traceable bug.

Core Features & Use Cases

  • Feature Mapping: Builds a map linking specification sections in _reversa_sdd/ to implementing code, existing tests, and touched data stores before any analysis begins.
  • Parallel Diagnostic Lenses: Runs mandatory lenses (spec conformance, data flow, contracts/integrations, error states, test coverage, concurrency) plus conditional lenses (security, performance, config drift, observability) as parallel subagents.
  • Central Bug Registration: Deduplicates findings, applies a strict confirmation criterion, and registers accepted bugs in _reversa_bugs/<context>/bugs/ with merge-safe IDs and full traceability.
  • Use Case: A legacy billing feature keeps producing wrong totals. Run this Skill to map the feature, sweep it with all lenses, and receive a report of findings plus registered bugs ready for fixing with /reversa-debugger-fix.

Quick Start

Ask the agent to run a deep inspection on the feature that keeps failing, for example: run reversa-depth-inspection on the billing feature.

Frequently Asked Questions about reversa-depth-inspection

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

FAQPage Schema
How do I run a deep inspection on a buggy feature?

Invoke the reversa-depth-inspection skill and name the target feature, or pick one from the known features in taxonomy.yaml when prompted. The skill maps specs, code, tests, and data first, then sweeps the feature with diagnostic lenses and reports confirmed bugs.

What does the depth inspection analyze in a codebase?

It analyzes six mandatory areas: spec conformance, data flow, external contracts and integrations, error states and edge cases, test coverage, and concurrency. Conditional lenses for security, performance, configuration drift, and observability activate only when the feature map shows relevant signals.

Does the inspection modify or fix my code?

No. The skill is strictly diagnostic and never corrects, refactors, or overwrites existing project files. It writes only new bug records, inspection reports, and generated views inside the _reversa_bugs/ directory.

Which AI coding agents support this skill?

The skill declares compatibility with Claude Code, Codex, Cursor, Gemini CLI, and other agents supporting the Agent Skills format. It is installed by the Reversa framework into .agents/skills/ and .claude/skills/ directories.

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

Use it when a feature repeatedly produces bugs and isolated fixes no longer suffice, since it sweeps the whole feature with multiple lenses. For a single known defect, the /reversa-debugger workflow is the more direct path.