verify-logic-parity

Verify backend game logic parity with legacy PHP and core2026 systems.

Updated May 29, 2026
One-click install
npx skills add https://github.com/peppone-choi/opensamguk --skill verify-logic-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-logic-parity
Source: https://github.com/peppone-choi/opensamguk/tree/main/.claude/skills/verify-logic-parity
Command: npx skills add https://github.com/peppone-choi/opensamguk --skill verify-logic-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that the new game engine logic in the backend produces the exact same results as the legacy PHP implementation for identical inputs, preventing regressions and ensuring consistency.

Core Features & Use Cases

  • Command Logic Verification: Compares the output of new backend commands against legacy and core2026 implementations.
  • Formula and Calculation Check: Validates that all in-game formulas and calculations are identical to the legacy system.
  • Turn Execution Order: Confirms that the sequence of game events and actions during a turn matches the legacy system.
  • Use Case: After implementing a new combat command, use this Skill to verify that the damage calculations, status effects, and turn order outcomes are precisely the same as they would be in the old system.

Quick Start

Run the verify-logic-parity skill to check the 'che_농지개간' command against legacy logic.

Frequently Asked Questions about verify-logic-parity

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

FAQPage Schema
How do I verify game logic parity between a new backend and a legacy PHP implementation?

Game logic parity verification compares command execution, turn order, constraints, formulas, and events between a new backend and legacy PHP systems to ensure identical outputs for the same inputs.

What is legacy migration parity checking for game engine logic?

Legacy migration parity checking is the process of validating that a new game engine backend produces exact same results as an old system. It covers command execution, formulas, and turn execution order to prevent behavioral regressions.

Can I check turn execution order and formulas against a core2026 system implementation?

Yes, you can check turn execution order and in-game formulas against a core2026 system implementation by comparing the sequence of game events, actions, and calculation constraints to confirm outcomes match precisely.

How do I prevent regressions when migrating game backend commands to a new engine?

Prevent regressions during game backend migration by verifying that newly implemented commands produce identical damage calculations, status effects, and turn order outcomes as the legacy PHP system for identical input scenarios.

Does backend verification for game logic require comparing code and documentation?

Yes, backend verification for game logic ensures parity by comparing both code and documentation to validate that command logic, formulas, and constraints in the new engine match legacy implementations accurately.