Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
Scanned 6/2/2026
Install to Claude Code
npx -y skills add majiayu000/claude-skill-registry --skill api-contract-checker --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Api Contract Checker Proflead Codex Skills Library?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-api-contract-checker-proflead-codex-skills-library)More formats (shields.io, HTML) on the badges page.
---
name: api-contract-checker
description: Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
---
# API Contract Checker
## Purpose
Validate API changes against an expected contract.
## Inputs to request
- Old and new API specs or examples.
- Versioning policy and client expectations.
- Known consumers and usage patterns.
## Workflow
1. Compare endpoints, request/response fields, and status codes.
2. Identify breaking changes and backward-compatible adjustments.
3. Suggest versioning or migration notes.
## Output
- Breaking change report with mitigation steps.
## Quality bar
- Flag any removal or behavior change clearly.
- Recommend safe rollouts for clients.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...