mastraudit

What problem does it solve?

Mastra-based codebases can drift into incompatible API usage and unclear ownership of Mastra wiring, causing brittle builds and hard-to-debug runtime behavior.

Core Features & Use Cases

• Current-docs correctness checks: Verifies Mastra implementation against the installed $mastra/Mastra documentation workflow rather than relying on memory.
• Deterministic boundary & structure audits: Detects incorrect mastra/@mastra imports, dependency boundary violations, Mastra CLI usage from non-approved packages, and misplaced Mastra-looking code outside the approved package.
• Actionable remediation guidance: Produces findings with severities, file paths, categories, and concrete next steps to move setup and domain code into the approved Mastra package.

Quick Start

Use the $mastraudit skill on the repository you want audited, and accept the remediation plan it returns for moving Mastra tooling into exactly one approved package with domain folders under src/.