reversa-reviewer

Audit reverse-engineering specifications for inconsistencies, gaps, and weak assumptions.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-reviewer-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-reviewer
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-reviewer
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-reviewer-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverse-engineering specifications generated by the reversa-writer often contain inconsistencies, gaps, and weak assumptions. The reviewer helps ensure quality and testability before human validation by systematically auditing these specs.

Core Features & Use Cases

  • Cross-check specifications within a unit and across multiple units to uncover contradictions.
  • Identify gaps and unaddressed edge cases critical for safe deployment.
  • Reclassify statements using a standardized confidence taxonomy and document evidence.
  • Use Case: A product team uses the reviewer to validate an inferred model against actual system behavior.

Quick Start

Review the latest generated specs, run the structured checks, and generate a set of targeted questions for human validation.

Frequently Asked Questions about reversa-reviewer

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

FAQPage Schema
How do I validate reverse-engineered specifications for internal consistency?

Validating reverse-engineered specifications involves cross-checking inferred models within units and across multiple units to uncover contradictions, identify unaddressed edge cases, and flag weak assumptions for human review.

What is cross-unit coherence checking in reverse-engineering?

Cross-unit coherence checking is the process of auditing reverse-engineered specifications across separate modules to ensure systemic consistency, capturing evidence of conflicts, and reclassifying confidence levels using a standardized taxonomy.

How do I find gaps and missing edge cases in inferred system behavior models?

Finding gaps in inferred system models requires systematically auditing reverse-engineered specifications to identify unaddressed edge cases critical for safe deployment, generating targeted validation questions to confirm actual behavior.

How do I reclassify confidence levels in reverse-engineering specifications?

Reclassifying confidence levels in reverse-engineering specifications requires applying a standardized taxonomy to documented statements, capturing supporting evidence, and flagging weak assumptions for subsequent human validation.

What is the best way to audit inferred models against actual system behavior?

Auditing inferred models against actual system behavior is best accomplished by running structured checks on generated reverse-engineering specifications, identifying inconsistencies, and producing targeted validation questions for human review.