| name | integration-checker |
| description | Inspect the integration points between frontend, backend, database, and external APIs. Use it to detect contract mismatches, missing environment variables, broken assumptions, or setup-order issues. |
Integration Checker
Purpose
Catch errors and omissions at system integration boundaries rather than focusing on isolated features.
Core Principles
- Check the input and output contract expected by each layer first.
- Prioritize mismatches in field names, types, status codes, and exception flow.
- Review environment variables, auth data, initialization order, and network routes together.
- Validate failure paths and empty-data cases, not just the success path.
- Separate local behavior from deployed-environment behavior.
- Judge integration by whether it honors the intended contract, not whether it merely "connects."
Inputs
- List of modules or systems involved
- API specs, type definitions, schemas, or environment variables
- Relevant code or config files
- Current error symptoms or concerns, if available
Workflow
- Identify the connected systems and the boundaries between them.
- Document request or response, event, and state-transfer contracts.
- Compare types, fields, status codes, error handling, and authentication flow.
- Check environment variables, config values, URLs, and secret injection points.
- Inspect initialization order, async handling, loading states, and retry behavior.
- Summarize the highest-risk integration points and how to validate them.
Output Format
Integration Summary
- Connected systems
- Boundaries under review
Contract Review Results
- Request or response interfaces
- Type or schema alignment
- Authentication and authorization flow
- Error-handling flow
Configuration and Environment Review
- Required environment variables
- Config files or runtime dependencies
- Environment-specific differences
Key Risks
- Likely mismatch points
- Items that could cause real incidents
- Areas that need more validation
Validation Plan
- Items to confirm via automated tests
- Items that need manual inspection
- Reproduction steps or logs to inspect
When Information Is Missing
- If no spec exists, separate code-based facts from inferences.
- If a contract mismatch is suspected, state which side should be treated as the source of truth.
- If the scope is too broad, prioritize from the outermost boundary inward.
