skills.rest
MiniMax-AI
MiniMax-AIOFFICIAL
Explore all skills by this author →
Website𝕏@MiniMax_AIGitHub

testing-workflow

Select and run repository test gates to verify MiniMax Code changes.

1.3k|142|Updated Jun 1, 2026
Search Tags:#vitest#testing#verification#pnpm#code validation#test workflow#ci gates
One-click install
npx skills add https://github.com/MiniMax-AI/minimax-code --skill testing-workflow-minimax-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-workflow
Source: https://github.com/MiniMax-AI/minimax-code/tree/main/.agents/skills/testing-workflow
Command: npx skills add https://github.com/MiniMax-AI/minimax-code --skill testing-workflow-minimax-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right verification steps for a change in a large repository is error-prone: contributors may run the wrong test suites, skip CI gates, or report unverified results. This Skill maps changed files to the repository's declared test suites and CI gates so verification is complete and correctly reported. ## Core Features & Use Cases - Gate Selection: Maps change scopes (runtime, TUI, providers, CLI artifact, sandbox, release tools) to the correct pnpm test gates and Vitest suite declarations. - Focused Iteration: Guides running individual Vitest files via the declared suite configuration instead of hard-coded test lists. - Delivery Verification: Covers pre-PR checks including git diff --check, pnpm verify on a clean commit, and source inventory regeneration. - Use Case: After modifying the headless CLI behavior, use this Skill to identify that pnpm test:byok is the owning gate, run it, and report PASS/FAIL results with manual evidence. ## Quick Start Ask the assistant to determine which test gates to run and how to report verification for the files changed in your current branch.

Frequently Asked Questions about testing-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a single Vitest test file in this repository?▼

Run pnpm exec vitest run --config vitest.oss.config.mjs followed by the test file path, for example packages/tui/test/unit/headless-contract.test.ts. Test files must be registered in test/vitest-suites.json rather than hard-coded in package scripts.

Which test gate should I run for my code change?▼

Match the change scope to its gate: runtime, TUI, providers and plugins use pnpm test:capabilities; headless CLI uses pnpm test:byok; CLI artifacts use pnpm test:smoke. Use pnpm verify --list to inspect all gates for the current platform.

What checks are required before opening a pull request?▼

Run pnpm verify on the reviewed commit with a clean tracked working tree, since source export reads committed HEAD and rejects uncommitted changes. Also run git diff --check and regenerate release/public-source.json if files were added or removed.

Why do artifact-dependent tests fail locally?▼

Artifact-dependent tests require a current pnpm build before running. Build first, then execute the owning gate such as pnpm test:artifact or pnpm test:smoke.

How should test results be reported for a change?▼

Report scope, commands, results, manual scenarios, and untested boundaries using PASS, FAIL, or BLOCKED for actual checks. Mark checks that did not run explicitly, and note that local macOS success does not establish Windows, Linux, or live-service acceptance.

Related Skills

Explore More Software Engineering Skills→
jacobrocks1212jacobrocks1212

stage

Partition uncommitted changes into commit-sized steps and stage them sequentially.

Community
Intermediate
inkeepinkeep

review

Manage the Pull Request review loop by polling feedback, assessing suggestions, and resolving CI/CD checks.

Official
Advanced
petbrainspetbrains
13

frontend-debug-linting

Lint, type-check, format, and verify React/Next.js projects in browsers.

Official
Intermediate
trystan2ktrystan2k
1

agent-ci

Runs GitHub Actions CI pipelines locally to validate code before pushing.

Community
Intermediate