Debug Mastra Framework
mastra-ai/mastra-smoke/.agents/skills/debug-mastra-framework
codingOfficial
Official Provider SkillView repo
Debug bugs inside the @mastra/* packages from the smoke suite. Use when a smoke test fails with a stack trace pointing at node_modules/@mastra/* or .mastra/output/*, when you see framework-specific error strings (keyValidator._parse, SQLITE_ERROR mastra_*, "Background task started" instead of a tool result, "Tool not found" 500s, ZodObject._parse crashes), or when the user asks to investigate a regression in the published alpha. This skill teaches you how to map a published version back to upstr
Files3 files
SKILL.md233 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the archive and add the files to your project manually.
Skill details
Versionv1.0.0
AuthorMastra AI
Categorycoding
Skill IDmastra-ai/mastra-smoke/.agents/skills/debug-mastra-framework
Files3 files
Related skills
Diagnose Smoke FailureDiagnose a failing Mastra smoke-test run when tagged on the failure thread in Slack (the channel running `mastra-ai/mastra-smoke`). Use this when you see a Slack message containing the literal token `SMOKE_FAILURE_CONTEXT` in a thread you've been mentioned in, when the user asks you to "debug this smoke run" / "look at the failure" / "diagnose this red build", or when a smoke-channel message links to a `github.com/mastra-ai/mastra-smoke/actions/runs/<id>` URL and asks for help. This skill teacheExtend Smoke CoverageAdd smoke-test coverage for a new Mastra feature, API route, or Studio UI surface. Use when the user asks to "add coverage for X", "write a smoke test for the new Y endpoint", "test the new Z page", when a Mastra release notes mention features not currently exercised, when investigating a regression that wasn't caught because there was no test for that path, or any time you are about to write or modify a `.test.ts` / `.spec.ts` file under `tests/` or `tests-ui/`. This skill explains where tests Code StandardsCode quality standards and style guide for reviewing pull requestsCoding AgentAuthoring playbook for building agents that write, edit, review, or refactor code. Use this when the user asks for an agent that writes scripts, generates code, reviews pull requests, refactors a codebase, fixes bugs, implements features, writes tests, or works with programming languages such as Python, TypeScript, JavaScript, Go, Rust, SQL, or shell.Docs AuditAutonomous, report-only documentation review for Mastra docs. Use when auditing changed docs against source, validating contextual code examples or API coverage, checking canonical mastra-docs guidance, or running narrow deterministic checks.E2e Tests StudioREQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.