# Mastra Smoke Test

Smoke test Mastra projects locally or deploy to staging/production.

- Repository: https://github.com/mastra-ai/mastra (29259 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add mastra-ai/mastra --skill mastra-smoke-test -g -a claude-code -y`
Codex: `npx skills add mastra-ai/mastra --skill mastra-smoke-test -g -a codex -y`
Cursor: `npx skills add mastra-ai/mastra --skill mastra-smoke-test -g -a cursor -y`
Gemini CLI: `npx skills add mastra-ai/mastra --skill mastra-smoke-test -g -a gemini-cli -y`

## Description

Smoke test Mastra projects locally or deploy to staging/production. Tests Studio UI, agents, tools, workflows, traces, memory, and more. Supports both local development and cloud deployments.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Mastra Smoke Test

Comprehensive smoke testing for Mastra projects.

## Release smoke workflows

Use progressive disclosure: stay in this file until the workflow branches, then read only the reference for the branch you are on. `references/release-smoke.md` is a short index if you need the full map.

### Alpha release branch point

Before alpha smoke testing, identify the alpha versioning PR state. Prefer the standard Changesets release branch:

```bash
gh pr view changeset-release/main \
  --json number,title,state,url,headRefName,baseRefName,isDraft,mergeable,reviewDecision,updatedAt,mergedAt,mergeCommit
```

Expected shape:

```text
title: chore: version packages (alpha)
head: changeset-release/main
base: main
```

If that branch lookup fails, search open and recently merged PRs:

```bash
gh pr list --state open --search 'version packages alpha in:title' --limit 20
gh pr list --state merged --search 'version packages alpha in:title' --limit 20
```

Then branch:

- If the versioning PR is **open**, read `references/alpha-versioning-pr.md`.
- If the versioning PR is **merged**, read `references/alpha-publish.md`.
- If no versioning PR exists, report that and wait for the scheduled alpha versioning flow or user direction.

Do not create the alpha smoke-test project until the automatic alpha publish workflow has completed and the intended packages are installable.

### Stable release branch point

If the user is running the stable/full release workflow, read `references/stable-release-smoke.md`. If that workflow fails after some packages publish, switch to `references/stable-partial-publish-recovery.md`.

### Scope and targeted checks

After the release package is published and before running smoke tests, read `references/release-scope-discovery.md` to identify changed features. Use the default generated project for the baseline checklist, then add targeted checks for changed features the generated project does not exercise.

The rest: https://github.com/mastra-ai/mastra/blob/HEAD/.claude/skills/mastra-smoke-test/SKILL.md