test-all
Run the FULL Momentum CMS test suite — every single suite, no skips. Triggers on "test all", "test everything", "run all tests", "run the test all script", "test-all script", "run the full suite", "run every test", "test the whole thing", "make sure everything passes", "run test:all", or ANY variation asking to run all/every/full tests. Also triggers on typos like "test al", "tets all", "tes all". NEVER skip suites unless the user EXPLICITLY names suites to skip.
Best use case
test-all is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run the FULL Momentum CMS test suite — every single suite, no skips. Triggers on "test all", "test everything", "run all tests", "run the test all script", "test-all script", "run the full suite", "run every test", "test the whole thing", "make sure everything passes", "run test:all", or ANY variation asking to run all/every/full tests. Also triggers on typos like "test al", "tets all", "tes all". NEVER skip suites unless the user EXPLICITLY names suites to skip.
Teams using test-all should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/test-all/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How test-all Compares
| Feature / Agent | test-all | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run the FULL Momentum CMS test suite — every single suite, no skips. Triggers on "test all", "test everything", "run all tests", "run the test all script", "test-all script", "run the full suite", "run every test", "test the whole thing", "make sure everything passes", "run test:all", or ANY variation asking to run all/every/full tests. Also triggers on typos like "test al", "tets all", "tes all". NEVER skip suites unless the user EXPLICITLY names suites to skip.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Full Test Suite Runner Runs **every** test suite in the Momentum CMS monorepo. **Do NOT skip any suite unless the user explicitly requests it.** ## CRITICAL: Trigger Recognition This skill MUST activate when the user says ANY of these (including typos and variations): - "test all", "test everything", "run all tests", "run every test" - "test-all script", "run the test all script", "run test:all" - "run the full suite", "test the whole thing", "make sure everything passes" - "run the full test suite", "execute all tests", "test it all" - Typos: "test al", "tets all", "tes all", "test alll" **When triggered, run `npm run test:all` with ZERO --skip flags. Period.** ## Command ```bash npm run test:all ``` This executes `npx tsx scripts/test-all.ts` which runs all suites sequentially. ## Available Suites | Name | Label | What It Runs | | --------------------- | ------------------- | --------------------------------------------------- | | `unit-tests` | Unit Tests | `nx run-many -t test --parallel=3` (all unit tests) | | `angular-e2e` | Angular E2E | `nx e2e example-angular-e2e` | | `analog-e2e` | Analog E2E | `nx e2e example-analog-e2e` | | `nestjs-e2e` | NestJS E2E | `nx e2e example-nestjs-e2e` | | `swappable-admin-e2e` | Swappable Admin E2E | `nx e2e test-swappable-admin-e2e` | | `migration-tests` | Migration Tests | `nx test migrations` | | `cli-scaffold` | CLI Scaffold Test | `npx tsx scripts/test-all.ts --database sqlite` | ## Usage ```bash # Run EVERYTHING (default — this is what "test all" means) npm run test:all # Run only one suite npm run test:all -- --suite angular-e2e # Skip specific suites (only if user explicitly asks) npm run test:all -- --skip cli-scaffold --skip analog-e2e ``` ## Rules 1. **When the user says "test all", "run test all", "test-all script", or similar — run `npm run test:all` with NO --skip flags.** Every suite must run. 2. Logs go to `/tmp/test-all/`. If a suite fails, read the log file to diagnose. 3. The script exits with code 1 if any suite fails. 4. Timeout should be generous (10 minutes) since E2E suites take time. 5. If a suite fails, report which suite failed and show the last ~30 lines of its log. ## Arguments - `$ARGUMENTS` — passed directly to the script (e.g., `--suite unit-tests`, `--skip cli-scaffold`). If empty, runs everything. ## Execution ```bash npm run test:all $ARGUMENTS ```
Related Skills
stroll-test
End-to-end CLI stroll test of npm-published Momentum CMS packages. Scaffolds a fresh project with create-momentum-app, adds all plugins, runs migrations, starts server, and verifies everything works. Triggers include "stroll test", "cli stroll", "test published packages", or "/stroll-test".
e2e-test
Write and validate Playwright E2E tests for Momentum CMS features. UI tests ALWAYS start from /admin dashboard and navigate via sidebar/dashboard — never go directly to deep URLs. Always starts the server and inspects the actual UI before writing assertions. Triggers include "write e2e tests for...", "add e2e tests", "test the admin UI for...", or "/e2e-test <feature>".
headless-ui
Use @momentumcms/headless inside generated Momentum apps. Use when building custom public UI, composing accessible primitives, configuring global styles for hdl-* elements, or adding app-level tests around headless interactions.
ui-audit
Comprehensive UI component audit for Momentum CMS. Use when asked to audit, review, check, or validate a UI component. Checks Storybook stories, interaction tests, variants, kitchen sink integration, admin dashboard usage, accessibility, and responsive design (mobile-first). AUTOMATICALLY FIXES issues found and verifies with visual inspection. Triggers include "audit button", "review the card component", "check accessibility of tabs", or "/ui-audit <component-name>".
skill-improve
Self-improving skill loop. Analyzes eval failures, rewrites the skill, re-evaluates, and repeats until convergence. Run after /skill-eval produces baseline results.
skill-eval
Run structured evaluations comparing skill vs no-skill performance. Measures assertion pass rates, timing, and output quality to systematically improve skills.
prepare-release
Prepare a patch/minor/major version release for all Momentum CMS packages. Bumps versions, generates changelogs, verifies builds/tests, adds new packages to Nx release config, and commits. Triggers include "prepare release", "bump version", "release patch", or "/prepare-release".
momentum-api
Work with Momentum API for data operations in Angular components
migrations
Run migrations, generate schemas, and manage code generation for Momentum CMS. Use when working with database migrations, Drizzle schema generation, type generation, or Angular schematics.
mcp-setup
Set up the Momentum CMS MCP server plugin and generate Claude Code MCP config for AI tool integration. Use when connecting Claude Code (or any MCP client) to a Momentum CMS instance.
SYSTEM ROLE & BEHAVIORAL PROTOCOLS
**ROLE:** Senior Frontend Architect & Avant-Garde UI Designer.
headless-primitive
Author, extend, or repair primitives in libs/headless. Use when adding a new headless primitive, changing its accessibility contract, updating slots/state attrs, wiring overlay behavior, or expanding the example styling lab and tests.