reversa-depth-inspection

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

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-depth-inspection-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-depth-inspection
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-depth-inspection
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-depth-inspection-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature keeps producing recurring problems, fixing one bug at a time is not enough. This Skill performs a deep, systematic inspection of an entire feature—mapping its specification, code, tests, and data—then sweeps it with specialized lenses to surface every confirmed defect as a registered, traceable bug, without ever modifying project code. ## Core Features & Use Cases - Feature Mapping: Builds a map linking spec sections (including active addenda) to implementing code, existing tests, and touched data stores before any analysis begins. - Parallel Specialized 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 when supported. - Confirmed-Bug Registration: Deduplicates findings against the existing bug catalog, applies a strict confirmation criterion, and registers accepted bugs in _reversa_bugs/<context>/bugs/ with merge-safe IDs and full traceability. - Use Case: A registration feature in a Reversa-framework project keeps failing in production. Run this Skill to map the feature, sweep it with all lenses, and receive a report of findings with confidence levels plus newly registered bug IDs ready for fixing. ## Quick Start Ask the agent to run a deep inspection on the feature that keeps causing problems, naming the target feature or choosing it from the offered list.

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 Skill and name the target feature, or pick it from the offered list of known features in the taxonomy. The Skill maps spec, code, tests, and data first, then sweeps with specialized lenses and presents confirmed bug candidates for your approval before registering them.

What does a spec-to-code inspection lens actually check?▼

The conformance lens compares implemented behavior against the effective spec (original plus active addenda). Other lenses check data flow errors, broken external contracts, error and edge-case paths, missing or vacuous test coverage, and concurrency issues like race conditions and missing idempotency.

Does the inspection modify or fix my project code?▼

No. The Skill only diagnoses and never corrects. It writes exclusively inside the _reversa_bugs directory—new bug records, the inspection report, and generated views—and is explicitly forbidden from editing, deleting, or refactoring any pre-existing project file.

How are inspection findings turned into registered bugs?▼

Findings from all lenses are merged, deduplicated against existing bugs, and filtered by a confirmation criterion requiring observable deviation or a complete static causal proof. You approve candidates via a menu, then accepted ones are registered serially with merge-safe IDs and origin type inspection.

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

Use it when a feature repeatedly produces problems and isolated fixes have not stabilized it. Deep inspection reveals clusters of related defects pointing to a common structural cause, whereas single-bug debugging addresses only one symptom at a time.