API Contract Validator
When to Use This Skill
Use for any endpoint behavior change, including new routes, payload changes, status code updates, or error handling changes.
Validation Workflow
- •Identify contract surface impacted (
/,/health, and any new endpoints). - •Verify expected status codes and JSON response shapes for success and failure paths.
- •Add/update unit tests that assert contract behavior (not internal implementation).
- •Verify unknown-route behavior remains intentional.
- •Confirm backward compatibility unless change is explicitly breaking.
- •Update root
README.mdif externally visible API behavior changed.
Contract Rules
- •Always return explicit status codes.
- •Keep response keys stable where possible.
- •Keep error payloads consistent across endpoints.
- •For breaking changes, document migration expectations in the root README.