parity-verify

Verify parity between legacy JSP/Java/Struts screens and React equivalents.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/ap05-epic/modernize-flow --skill parity-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parity-verify
Source: https://github.com/ap05-epic/modernize-flow/tree/main/skills/parity-verify
Command: npx skills add https://github.com/ap05-epic/modernize-flow --skill parity-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, playwright, pixelmatch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of verifying that a React application created with the jsp2react framework accurately replicates the functionality of its legacy JSP/Java/Struts counterpart.

Core Features & Use Cases

  • Automated Screen Verification: Performs both structural and visual comparisons between legacy and React screens.
  • Data Presence Check: Ensures that React renders the real data from the legacy application.
  • Use Case: After implementing a screen in the jsp2react flow, use this Skill to automatically verify the screen's parity against the legacy application.

Quick Start

Use the parity-verify skill to verify the parity of the screen for 'f010_default'.

Frequently Asked Questions about parity-verify

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

FAQPage Schema
How do I verify React parity with legacy JSP screens?

React parity with legacy JSP screens is verified using automated structural and visual comparisons. The process applies DOM and pixel comparisons to ensure the React application accurately replicates the legacy JSP/Java/Struts counterpart.

What is automated screen verification for jsp2react applications?

Automated screen verification for jsp2react applications is the process of comparing legacy and React screens to ensure functional replication. It performs structural DOM comparisons and visual pixel checks to validate data presence and rendering accuracy.

Do I need Python and Playwright to perform DOM and pixel comparisons?

Yes, you need Python 3, Playwright, and the pixelmatch library to perform automated DOM and pixel comparisons. These dependencies are required to execute the structural and visual checks between the legacy and React screens.

How do I check if my React screen renders real data from the legacy application?

To check if your React screen renders real data from the legacy application, you perform a data presence check. This automated verification ensures the React equivalent accurately displays the data from the legacy JSP/Java/Struts screen.

What's the best way to automate testing of jsp2react application parity checks?

The best way to automate testing of jsp2react application parity checks is by running a skill that applies both structural and visual comparisons. This validates screen parity by executing automated DOM and pixel comparisons using Playwright and pixelmatch.

When do I need to perform a structural and visual comparison between legacy and React screens?

You need to perform a structural and visual comparison between legacy and React screens after implementing a screen in the jsp2react flow. This verifies that the new React screen accurately replicates the legacy JSP/Java/Struts functionality.