Verified:GitHub

reversa-inspector

Generate parity specs and Gherkin parity scenarios for legacy-to-target migrations.

Updated May 5, 2026

Search Tags:#architecture #migration #gherkin #test specifications #behavioral parity #screen validation #equivalence validation

Ready to run

npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-inspector-alexandrepontesjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/AlexandrePontesjr/calculadora-Juridica/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-inspector-alexandrepontesjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents risky cutovers by defining how to demonstrate that the new system is behaviorally equivalent to the legacy system where it matters most.

Core Features & Use Cases

Parity-spec generation: Produces parity_specs.md capturing the chosen equivalence strategy, observation windows, primary metrics, and cutover-blocking criteria.
Paradigm-aware coverage: Adapts required parity dimensions (e.g., idempotency, ordering, invariants, immutability, supervision) based on the target paradigm decision.
Gherkin parity test specifications: Creates parity_tests/*.feature as non-executable, traceable Gherkin scenarios derived from critical legacy flows, including optional screen parity scenarios.

Quick Start

Use the reversa-inspector skill to generate parity specs and Gherkin parity scenarios after confirming the migration strategy and target architecture, so the handoff to the coding/orchestration step is evidence-based.

Frequently Asked Questions about reversa-inspector

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

FAQPage Schema

How do I prove behavioral equivalence between a legacy system and a migrated target?▼

To prove behavioral equivalence during a system migration, generate parity specifications and Gherkin-based parity scenarios derived from critical legacy flows, ensuring the new system matches observed business rules before cutover.

What is behavioral parity testing in software migration?▼

Behavioral parity testing validates that a migrated target system functions equivalently to its legacy counterpart by defining equivalence strategies, observation windows, and cutover-blocking criteria to prevent risky deployments.

How do I write Gherkin test specifications for migration parity validation?▼

Write Gherkin test specifications for migration parity by characterizing legacy flows and translating them into traceable, non-executable feature files that enforce paradigm-specific dimensions like idempotency, ordering, and immutability.

Does paradigm transition affect migration parity validation requirements?▼

Paradigm transitions directly affect migration parity validation by requiring adapted coverage dimensions, enforcing specific invariants like supervision or immutability based on the chosen target architecture's paradigm rules.

When do I need parity specifications for a system migration?▼

You need parity specifications for a system migration when paradigm transition decisions, legacy flow characterization, and target business rules are confirmed, producing evidence-based specs before handoff to the coding step.

Can I include screen validation in my migration parity specifications?▼

Yes, you can include screen validation in migration parity specifications by generating optional visual, golden, or contract screen parity scenarios within your Gherkin feature files to verify interface equivalence.