reversa-inspector

Generates parity specifications and Gherkin tests for system migration.

Updated May 8, 2025
One-click install
npx skills add https://github.com/ggazzo/brewpilot --skill reversa-inspector-ggazzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/ggazzo/brewpilot/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/ggazzo/brewpilot --skill reversa-inspector-ggazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of proving behavioral equivalence between legacy and new systems during and after migration, using criteria adapted to the chosen paradigm.

Core Features & Use Cases

  • Parity Specification Generation: Produces parity_specs.md and parity_tests/*.feature in Gherkin format.
  • Inspector Role: Acts as the fifth and final agent in the Migration Team, defining how to verify behavioral equivalence.
  • Use Case: For a system migration, the Skill generates parity specifications and tests to ensure the new system behaves identically to the legacy system.

Quick Start

Activate the Skill with the command: /reversa-inspector

Frequently Asked Questions about reversa-inspector

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

FAQPage Schema
How do I verify behavioral equivalence between legacy and new systems during migration?

Behavioral equivalence verification requires generating parity specifications and tests that compare legacy and new system behaviors. This Skill produces parity_specs.md and Gherkin-format feature files to validate identical execution outcomes based on tailored criteria.

Can I generate Gherkin feature files for parity testing automatically?

Yes, Gherkin feature files for parity testing are generated automatically as parity_tests/*.feature files. The Skill translates behavioral equivalence criteria into executable Gherkin scenarios to validate system migration accuracy.

What documents do I need to prepare for parity specification generation?

You need to provide access to migration strategy documents and system design specifications. These inputs allow the Inspector to adapt verification criteria to the chosen paradigm and generate accurate parity specifications.

What is the role of parity testing in a system migration strategy?

Parity testing defines how to verify behavioral equivalence between legacy and new systems. It acts as the final validation step in a migration team, ensuring the migrated system behaves identically to the original.

Does reversa-inspector adapt verification criteria for different architectural paradigms?

Yes, the Inspector adapts parity verification criteria to the chosen architectural paradigm. It tailors the generated specifications and tests to match the specific system design and migration strategy provided.

What output formats are produced when generating system verification tests?

The Skill produces a parity_specs.md markdown file detailing the equivalence criteria and parity_tests/*.feature files containing Gherkin scenarios. These outputs document and automate the behavioral verification process.