skills.rest
Pabloprogramador23
Pabloprogramador23COMMUNITY
Explore all skills by this author →
GitHub

reversa-inspector

Define migration parity criteria and generate parity_specs.md with .feature files.

Updated Jun 6, 2026
Search Tags:#validation#specifications#migration#parity#parity-specs#parity-tests
One-click install
npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-inspector-pabloprogramador23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-inspector
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa-inspector
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-inspector-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Inspector helps engineering teams confirm that migrated systems preserve the same behavior as the legacy system, guiding the creation of formal parity artifacts and preventing drift during transition.

Core Features & Use Cases

  • Defines a parity strategy tailored to the chosen migration paradigm and outputs parity_specs.md plus a set of parity_tests/*.feature for critical flows.
  • Reuses characterization_specs when available to anchor validations, or derives critical flows from analysis and migration rules.
  • Produces auditable, traceable specs with spec-id mappings and links to target architecture and paradigm decisions.

Quick Start

Run the inspector against the migration plan to generate parity_specs.md and parity_tests/*.feature for the chosen paradigm.

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 parity during a system migration?▼

Parity tests validate that a migrated system matches legacy behavior by producing non-executable .feature files for human review. These tests define critical flows and validation modes to ensure functional equivalence.

What is a parity specification for migration validation?▼

A parity specification documents how to prove a new system behaves identically to a legacy system. It produces a parity_specs.md file with spec-id mappings and links to target architecture decisions for auditable traceability.

How do I create parity tests for critical migration flows?▼

You create parity tests by running validation against your migration plan to generate .feature files. It reuses available characterization_specs or derives critical flows from analysis to anchor behavioral validations.

When do I need formal parity criteria for a migration?▼

You need formal parity criteria when a migration involves paradigm changes that require strict behavioral equivalence. Defining a tailored parity strategy with auditable specs prevents functional drift between legacy and target systems.

Does the parity validation output executable test scripts?▼

No, the parity validation outputs non-executable .feature files designed for human review. These traceable artifacts are stored under the _reversa_sdd/migration directory with frontmatter-based metadata for auditing purposes.

Related Skills

Explore More Software Engineering Skills→
satsuki-64satsuki-64
2

research-refine

Convert vague research directions into concrete problem anchors and method plans.

Community
Advanced
RheasilviaRheasilvia

test-driven-development

Enforce the Red-Green-Refactor cycle with automated tests via terminal.

Community
Advanced
erwaenerwaen

scaffold-model

Generate Rails model scaffolds with migration, validations, associations, scopes, and RSpec specs.

Community
Advanced
cliffthelincliffthelin

reversa-inspector

Generate paradigm-adapted parity specifications and Gherkin scenarios for Reversa migrations.

Community
Advanced