integration-check

Analyze export-to-import, route, auth guard, and store wiring in Vue/Nuxt projects.

1|Updated Mar 18, 2026

Search Tags:#integration #routing #vue #auth #nuxt #wiring

Ready to run

npx skills add https://github.com/lasswellt/cc-plugin-suite --skill integration-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-check
Source: https://github.com/lasswellt/cc-plugin-suite/tree/main/skills/integration-check
Command: npx skills add https://github.com/lasswellt/cc-plugin-suite --skill integration-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-module wiring validation for multi-module codebases by tracing exports to importers, ensuring route coverage, auth guard presence, and store-to-component wiring, all via read-only analysis.

Core Features & Use Cases

Export-to-import tracing: verify every exported symbol has at least one consumer.
Route coverage: ensure navigation paths exist for defined routes and pages.
Auth guard coverage: detect routes/endpoints that require authentication and verify guards exist.
Store-to-component wiring: confirm stores/composables are consumed by components.

Quick Start

Run the integration-check against your project to generate a findings report.

Frequently Asked Questions about integration-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate cross-module wiring in a multi-module Vue or Nuxt app?▼

Validate cross-module wiring by running a read-only static analysis of TypeScript and Vue source files. It traces export-to-import relationships to confirm every exported symbol has a consumer and produces a structured findings report for remediation.

How do I check route coverage and auth guard presence across multiple Nuxt modules?▼

Check route coverage and auth guard presence by using an optional scope selector to focus on routes or auth. The analysis detects navigation paths, verifies guards exist for protected endpoints, and reports missing coverage.

What is the best way to verify store-to-component wiring in a multi-module codebase?▼

The best way to verify store-to-component wiring is to run a project-wide static analysis that confirms your stores and composables are actively consumed by components. It operates in read-only mode and outputs a structured report of any disconnected wiring.

Can I run static analysis on only the exports or stores in my multi-module Vue project?▼

Yes, you can run static analysis on only exports or stores by using the optional scope selector. This allows you to focus the read-only validation specifically on routes, exports, auth, or stores rather than running all checks at once.

Does cross-module wiring validation modify my TypeScript or Vue source files?▼

Cross-module wiring validation does not modify your TypeScript or Vue source files because it operates strictly in a read-only mode. It analyzes the project statically and outputs a structured report of findings to guide your manual remediation.

Why does my multi-module app have exported symbols with no consumers?▼

Exported symbols with no consumers occur when modules are disconnected during refactoring. Running an export-to-import trace validates cross-module wiring by identifying these orphaned exports and highlighting them in a structured findings report for cleanup.