Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/integration-checker
Verify cross-component wiring and data flow.
Passed 13 of 17 test cases with the skill, and 10 of 17 without it.
and 2 more in the full report
5 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
A Go handler in `api/handlers.go` is imported inside `routes/api.go` but never invoked or referenced anywhere in `routes/api.go`. What classification label applies to this export?
| Checked | Without skill | With skill |
|---|---|---|
| Classifies an imported symbol with zero calls or references as IMPORTED_NOT_USED. | Missed | Passed |
The instructions your model reads when the skill loads.
Check that components are connected and receive real data. A function can pass unit tests yet never be called; an endpoint can exist without being registered.
This skill reads and reports. Return fixes to the active implementation task or feature-lifecycle; do not create another approval round when fixes are already authorized.
Load references/wiring-checks.md for language detection, export exclusions, wiring states, data-flow failures, contract patterns, and the requirements map.
Read repository instructions. In a feature pipeline, use .feature/state/implement/ to scope changed and added files. Otherwise use the requested path or diff; a requested full audit covers all source files. If the implementation artifact is missing, use the diff and state the gap.
Detect every language in scope. Reuse existing integration evidence for unchanged connections; trace affected producers and consumers beyond the diff where needed.
Gate: Scope and languages are known.
Inventory public symbols using language-aware searches:
__all__, and __init__.py re-exports.Exclude dependencies, generated files, build output, fixtures, and repository metadata. Apply the reference's exceptions for public library APIs, plugin contracts, framework entrypoints, and other legitimate external consumers before calling a symbol orphaned.
For each symbol, record file, name, kind, and line. Find imports and actual usage; an import alone does not establish wiring. Classify as ORPHANED, IMPORTED_NOT_USED, or WIRED using the reference. Report failures first; show successful connections only in verbose mode.
Gate: Every in-scope symbol has a status or an explicit unresolved limitation.
Trace WIRED connections for real inputs and compatible contracts. Check hardcoded empty data, placeholders, dead parameters, mock remnants, shape/type mismatches, and event/message names using the reference.
Static inspection establishes structure and likely compatibility, not runtime correctness. Use existing runtime evidence where available; distinguish observed failures from uncertain dynamic-language matches. Low-confidence contract findings warn rather than fail.
Gate: Data-flow and contract findings include locations, evidence, and confidence.
test cases passed, vs 10 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.