API Parity Skill

Validate one-to-one mapping between CLI commands and Library API implementations.

2|1|Updated Dec 26, 2025

Search Tags:#code quality #testing #consistency #api #cli #parity

Ready to run

npx skills add https://github.com/1ambda/dataops-platform --skill api-parity-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: API Parity Skill
Source: https://github.com/1ambda/dataops-platform/tree/main/.copilot/skills/api-parity
Command: npx skills add https://github.com/1ambda/dataops-platform --skill api-parity-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents API omissions by automatically verifying a one-to-one correspondence between CLI commands and Library API implementations, ensuring all intended functionalities are accessible through both interfaces.

Core Features & Use Cases

Automated Verification: Checks for the existence of corresponding API files, classes, exports, and test files for each CLI command module.
Gap Identification: Clearly flags missing API components or tests, providing specific error messages and evidence.
Use Case: When a new CLI command for data lineage is developed, this Skill automatically checks if the LineageAPI class and its associated test file exist, preventing a gap in API coverage.

Quick Start

Run the API parity check to ensure all CLI commands have corresponding API implementations.

Frequently Asked Questions about API Parity Skill

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

FAQPage Schema

How do I check CLI commands for missing API implementations?▼

Verify CLI command and API parity by scanning CLI modules against expected API classes, export statements, and test files to identify gaps in functionality coverage and prevent API omissions.

What is API parity and why do I need it for my library?▼

API parity is a one-to-one mapping between CLI commands and Library API implementations that ensures all features exposed via the CLI are also programmatically accessible, maintaining code quality and developer experience.

How do I verify that all my CLI features have corresponding API classes?▼

Run an automated verification check that confirms the existence of corresponding API files, classes, exports, and test files for each CLI command module, clearly flagging any missing components with specific evidence.

Can I automatically flag missing test files for my CLI commands?▼

Yes, you can flag missing test files by validating the one-to-one mapping between CLI modules and expected API test files, providing specific error messages and evidence for the gaps.

What is the best way to maintain consistency between a CLI and a Library API?▼

The best way to maintain CLI and Library API consistency is to automatically verify a one-to-one correspondence between command modules and API implementations, ensuring all intended functionalities are accessible through both interfaces.