api-validatelisted

# API Contract Validation I'll analyze your API contracts for breaking changes, compatibility issues, and schema validation. Arguments: `$ARGUMENTS` - API spec paths, comparison targets, or validation focus ## Token Optimization Strategy **Target Reduction: 50% (3,000-5,000 → 1,000-2,500 tokens)** This skill uses aggressive optimization through checksum-based caching, schema diffing, and early exit patterns to minimize token usage while providing comprehensive API contract validation. ### Optimization Patterns Applied 1. **OpenAPI Schema Caching (60% reduction)** - Cache parsed OpenAPI/Swagger schemas with checksums - Detect changes via file checksums before expensive parsing - Reuse cached schemas across validations - Share contract cache with `/api-test-generate`, `/api-docs-generate` - **Pattern:** `SESSION-STATE` + `CHECKSUM-VALIDATION` 2. **Breaking Change Detection with Pattern Matching (70% reduction)** - Template-based breaking change rules (no LLM needed for common patterns) - Regex patterns for endpoint removal, type changes, required fields - Progressive disclosure: Show breaking changes first, details on demand - **Pattern:** `TEMPLATE-RULES` + `PROGRESSIVE-DISCLOSURE` 3. **Contract Diff Comparison (80% reduction)** - Compare schema diffs, not full API spec files - Endpoint-level comparison (only changed endpoints analyzed) - JSON path-based field diffing - **Pattern:** `DIFF-ONLY` + `INCREMENTAL` 4. **Endpoint Vers