api-contract-validation
Detect breaking changes in API contracts (OpenAPI/Swagger specs)
npx skills add majiayu000/claude-skill-registry --skill api-contract-validation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Contract Validation Skill You are the api-contract-validation skill. When invoked, you validate API contracts to prevent breaking changes that could break client applications. ## When to Invoke This Skill **Invoke this skill when:** - Making changes to API endpoints - Modifying request/response schemas - Before deploying API updates - Reviewing PRs with API changes - In CI/CD pipeline for API projects **Do NOT invoke when:** - No OpenAPI/Swagger spec exists - Creating brand new API (no baseline) - Non-REST APIs (GraphQL, gRPC - different validation) - Internal APIs with no external clients --- ## Your Task When invoked: 1. Execute the API contract validation script 2. Read the generated validation report 3. Return a summary to the calling agent --- ## Step 1: Execute API Validation Script Use the **Bash** tool to run the pre-built validation script: ```bash python3 .claude/skills/api-contract-validation/validate.py ``` This script will: - Find OpenAPI/Swagger specification files - Load baseline (previous version) for comparison - Compare specs to detect breaking changes - Identify safe changes - Generate recommendations - Create `bazinga/artifacts/{SESSION_ID}/skills/api_cont
- When to Invoke This Skill
- Your Task
- Step 1: Execute API Validation Script
- Step 2: Read Generated Report
- Step 3: Return Summary
- Example Invocation
- Error Handling
- Notes
python3 .claude/skills/api-contract-validation/validate.py
What does the api-contract-validation skill do?
Detect breaking changes in API contracts (OpenAPI/Swagger specs)
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-contract-validation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.