Audit method presence and response shape parity across CLI, API, and MCP surfaces.
npx skills add https://github.com/jamesaphoenix/tx --skill surface-parity
Please help me install this Agent Skill. Skill: surface-parity Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/surface-parity Command: npx skills add https://github.com/jamesaphoenix/tx --skill surface-parity
Ensures shape and behavior parity across CLI, API, and MCP by auditing surface methods, aligning response shapes, and guiding repeatable fixes in an internal loop that keeps surfaces in sync without shipping to users.
Run the parity loop across CLI, API, and MCP to audit, fix gaps, and re-audit until parity is achieved.
High-intent search queries and answers about installing and using this skill.
Surface parity is the practice of ensuring method presence and consistent response shapes across CLI, API, and MCP interfaces. It prevents behavior gaps by auditing naming and shape alignment before cross-surface releases.
You enforce consistent response shapes by running the parity audit loop, which detects shape gaps across CLI, API, and MCP interfaces and guides iterative fixes to normalize naming and align behavior for identical responses.
Yes, the parity audit requires maintaining alignment with eslint rules tx/require-surface-parity and tx/interface-parity to validate readiness and enforce method presence and consistent response shapes across CLI, API, and MCP domains.
You need to run a cross-surface parity audit before cross-surface releases and during refactors. It validates readiness by detecting missing methods, shape gaps, and behaviour gaps across CLI, API, and MCP to prevent shipping inconsistencies.
The best way to resolve behavior gaps is to execute the parity audit repeatedly, allowing it to guide iterative fixes that fill shape gaps, normalize naming, and align behavior across API and CLI until all surfaces are in sync.
paritytechAutomate Polkadot application development using @parity/product-sdk packages.
clineCoordinate multiple specialized code reviewers to analyze pull requests.
GantisStormDefine canonical plan file schemas with required sections and naming conventions.
saintgo7Validate FastAPI routes, response schemas, and status codes against a committed OpenAPI snapshot.
