reversa-reviewer

Validate reverse-engineered technical specifications against source code and architectural patterns.

Updated May 19, 2026
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-reviewer-silaslopes100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-reviewer
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-reviewer
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-reviewer-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the risk of inaccurate or incomplete technical specifications generated during reverse engineering by providing a structured, multi-layered review process.

Core Features & Use Cases

  • Cross-Review Integration: Optionally delegates independent validation to the Codex engine to identify inconsistencies and logic gaps.
  • Confidence Classification: Systematically categorizes assertions as Confirmed, Inferenced, or Lacuna based on source code evidence.
  • Interactive Validation: Generates targeted questions for human stakeholders to resolve critical ambiguities in the documentation.
  • Use Case: Use this skill after generating a suite of technical specs to ensure that all requirements, design decisions, and task lists are consistent with the actual codebase and to identify missing business logic.

Quick Start

Run the reversa-reviewer skill to audit the current documentation folder and generate a confidence report.

Frequently Asked Questions about reversa-reviewer

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

FAQPage Schema
How do I validate technical specifications generated from reverse engineering?

Technical specification validation cross-references generated documentation against source code and architectural patterns to identify inconsistencies, classify confidence levels, and generate targeted validation queries for human stakeholders.

What is confidence classification in reverse-engineered documentation?

Confidence classification in reverse-engineered documentation systematically categorizes assertions as Confirmed, Inferenced, or Lacuna based on the available source code evidence to ensure high-fidelity technical specs.

How do I check reverse-engineered specs for missing business logic?

Checking reverse-engineered specs for missing business logic requires running a structured multi-layered review process that audits the documentation folder, identifies logic gaps, and generates a confidence report for stakeholders.

Does independent code review work with reverse-engineered technical specs?

Independent code review validates reverse-engineered technical specs by delegating cross-review integration to an independent engine that identifies inconsistencies and logic gaps through automated matrix validation.

When do I need to generate validation queries for technical documentation?

You need to generate validation queries for technical documentation when critical ambiguities are identified during the spec review process, requiring targeted questions to help human stakeholders resolve inconsistencies.

What are the limitations of automated matrix validation for code documentation?

Automated matrix validation for code documentation cannot resolve critical ambiguities independently; it requires generating targeted validation queries for human stakeholders to address missing business logic and classify uncertain assertions.