Coordinate API contract changes through validation, testing, and review.
npx skills add https://github.com/lgzarturo/codeconductor --skill cc-api-contract
Please help me install this Agent Skill. Skill: cc-api-contract Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-api-contract Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-api-contract
Run the API contract workflow to manage request/response shape changes, compatibility constraints, contract tests, documentation, and review.
Submit the API change request to initiate the contract workflow from validation to completion.
High-intent search queries and answers about installing and using this skill.
Managing API contract changes requires coordinating validation, technical planning, implementation, contract tests, and review. This workflow tracks approvals and migration plans to ensure backward compatibility and traceability across teams from initial request to completion.
An API contract workflow validates request and response shape changes, applies compatibility checks, runs contract tests, and updates documentation. It specifies required steps from validation through review to ensure backward compatibility and traceability during API evolution.
Validating API change scope involves submitting the API change request with task cards to initiate the contract workflow. This validates scope, defines contract tests, and assesses documentation impact before technical planning and implementation begin.
Yes, backward compatibility checks are integral to this API contract workflow. The process specifies validation, implementation, and contract test steps that ensure request and response shape changes maintain backward compatibility and produce required documentation and migration outputs.
Tracking API documentation and migration plan updates is handled by the contract workflow's review phase. It generates required documentation and migration outputs, ensuring traceability and tracking approvals across teams for API evolution scenarios.
Contract tests for API compatibility are needed during API evolution scenarios involving request or response shape changes. The workflow specifies running contract tests after implementation and before review to validate backward compatibility and documentation accuracy.
EONMUNConvert clarified specifications into technical plans with architecture, data models, and API contracts.
YokhanUpdate API endpoint contracts, implementations, tests, and documentation.
CleanExpoValidate Next.js App Router API endpoints against Zod schemas and security checks.
grtninjaValidate ranking report schema conformance and stabilize Ranking Engine contracts.
