# Integration Checker

> 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.

- Skill: `lteawoo/integration-checker` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lteawoo/integration-checker`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lteawoo/integration-checker/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: lteawoo (https://skillmd.com/u/lteawoo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lteawoo/integration-checker

---


# Integration Checker

## Purpose
Catch errors and omissions at system integration boundaries rather than focusing on isolated features.

## Core Principles
1. Check the input and output contract expected by each layer first.
2. Prioritize mismatches in field names, types, status codes, and exception flow.
3. Review environment variables, auth data, initialization order, and network routes together.
4. Validate failure paths and empty-data cases, not just the success path.
5. Separate local behavior from deployed-environment behavior.
6. 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
1. Identify the connected systems and the boundaries between them.
2. Document request or response, event, and state-transfer contracts.
3. Compare types, fields, status codes, error handling, and authentication flow.
4. Check environment variables, config values, URLs, and secret injection points.
5. Inspect initialization order, async handling, loading states, and retry behavior.
6. 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.