verify-command-parity

Verify game command parity across PHP definitions, Kotlin backend, and frontend UI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all game commands, originally defined in legacy PHP, are consistently and correctly implemented across the backend and frontend of the OpenSamguk project, preventing inconsistencies and missing features.

Core Features & Use Cases

  • Command Implementation Verification: Checks if 93 legacy commands (55 for generals, 38 for nations) have corresponding implementations in the backend (Kotlin).
  • Frontend UI Check: Verifies that implemented backend commands are selectable and executable in the frontend.
  • Registry Consistency: Ensures all backend commands are properly registered.
  • Documentation Sync: Compares implementation status with documentation (legacy-commands.md).
  • Use Case: After a developer implements a new general command like che_recruit, this Skill can be run to confirm it exists in the backend code, is registered, and is available for selection in the game's UI.

Quick Start

Run the verify-command-parity skill to check the implementation status of all game commands.

Frequently Asked Questions about verify-command-parity

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

FAQPage Schema
How do I verify game commands are implemented across backend and frontend?

To verify game command implementation, this Skill checks the parity of legacy PHP definitions against current Kotlin backend implementations and frontend UI availability, confirming all commands are fully registered.

What is command parity checking in game development?

Command parity checking is the process of ensuring legacy game commands are consistently implemented across backend code, frontend UI, and command registries, preventing inconsistencies and missing features during migration.

How do I sync documentation with actual command implementation progress?

You can sync documentation with implementation progress by running this Skill to compare the actual status of backend and frontend command implementations against the records in your legacy command documentation.

Can I check if legacy PHP commands have corresponding Kotlin backend implementations?

Yes, this Skill verifies the existence of 93 legacy PHP commands, including 55 general and 38 nation commands, ensuring they have matching implementations in the current Kotlin backend environment.

Does command parity verification include frontend integration checks?

Yes, command parity verification includes frontend integration checks to ensure that backend commands are properly registered and selectable within the game's frontend user interface.

What are the limitations of automated code verification for game commands?

Automated code verification for game commands is limited to checking existence and registration across backend, frontend, and documentation, without validating the functional logic or runtime behavior of the command implementations.