reversa-inspector

Generate parity specifications and Gherkin feature files for system migrations.

Updated May 11, 2026
One-click install
npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-inspector-marcu-loreto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/Marcu-Loreto/Skill_v1/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-inspector-marcu-loreto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of proving behavioral equivalence between legacy and new systems, producing parity specs and tests to facilitate smooth migration.

Core Features & Use Cases

  • Parity Specification Generation: Automatically produces parity_specs.md and parity_tests/*.feature files in Gherkin format.
  • Adaptation to Paradigm: Adjusts criteria for parity based on the chosen paradigm, ensuring comprehensive testing.
  • Pre-requisite Validation: Checks for the necessary pre-requisites like migration strategy, target architecture, and business rules before activation.

Quick Start

Run the /reversa-inspector command to initiate the parity specification generation process.

Frequently Asked Questions about reversa-inspector

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

FAQPage Schema
How do I generate parity specifications for a legacy system migration?

Equivalence testing for system migration requires validating behavioral parity between legacy and new architectures. This Skill automates generating parity specifications and Gherkin feature files, ensuring the new system accurately mirrors the original business rules and functions.

What prerequisites are needed to automate behavioral equivalence testing?

To automate behavioral equivalence testing, you need a defined migration strategy, target architecture, and established business rules. The Skill validates these prerequisites before generating parity specifications and Gherkin tests to ensure your system migration is properly prepared.

Can I generate Gherkin feature files for code migration parity checks?

Yes, you can generate Gherkin feature files for code migration parity checks. The Skill outputs parity_tests/*.feature files formatted in Gherkin, allowing you to execute automated equivalence testing and verify behavioral parity between legacy and new systems.

When do I need to use parity specifications during a system migration?

You need parity specifications during a system migration when you must prove behavioral equivalence between legacy and new environments. This Skill adjusts parity criteria based on your chosen paradigm, producing detailed specs and tests to facilitate a smooth, verifiable migration.

What is the best way to document behavioral parity between legacy and new systems?

The best way to document behavioral parity is by generating a comprehensive parity_specs.md file alongside Gherkin feature tests. This Skill automates that documentation process, providing clear specifications that prove your new system matches the legacy behavior.