Audit JavaScript and TypeScript repositories for Mastra implementation correctness and structural boundaries.
npx skills add https://github.com/howells/skills --skill mastraudit
Please help me install this Agent Skill. Skill: mastraudit Source: https://github.com/howells/skills/tree/main/mastraudit Command: npx skills add https://github.com/howells/skills --skill mastraudit
Mastra-based codebases can drift into incompatible API usage and unclear ownership of Mastra wiring, causing brittle builds and hard-to-debug runtime behavior.
$mastra/Mastra documentation workflow rather than relying on memory.mastra/@mastra imports, dependency boundary violations, Mastra CLI usage from non-approved packages, and misplaced Mastra-looking code outside the approved package.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/.
High-intent search queries and answers about installing and using this skill.
Auditing Mastra implementation correctness requires deterministic scanning of your TypeScript monorepo to compare installed API usage against current `$mastra` documentation and verify architectural boundaries. The Skill validates that only one package owns `mastra/@mastra` dependencies and imports.
Unclear Mastra dependency ownership causes brittle builds and hard-to-debug runtime behavior due to incorrect imports and CLI usage. Deterministic boundary scanning detects when Mastra wiring is scattered across non-approved packages and provides remediation guidance.
Enforcing domain folder structures involves scanning source directories to verify expected domain organization under `src/` and checking import statements. The audit identifies misplaced Mastra-looking code outside the approved package and flags dependency boundary violations.
Checking against current Mastra documentation is supported by comparing your installed implementation to the active `$mastra` guidance. This ensures API usage correctness by validating your codebase against the latest workflow rather than outdated knowledge.
Fixing Mastra architecture boundary violations involves following actionable remediation guidance that includes severities, file paths, and concrete next steps. The audit output directs you to move setup and domain code into the single approved Mastra package.
The Mastra architecture audit applies to both standard JavaScript and TypeScript repositories as well as multi-package monorepo workspaces. It validates Mastra API usage, dependency boundaries, and domain-folder organization across your entire project structure.
reactiveSet up Node.js, Yarn, and workspace commands for the Reactive Data Client monorepo.
mastra-aiEnforce Mastra brand colors, typography, and writing guidelines across documentation drafts.
pax-kEnforce and document architecture boundaries using dependency-cruiser, ESLint, import-linter, and custom scripts.
matthewharwoodAnalyze JavaScript or TypeScript repositories for unused code and structural issues.