メニュー
Test frameworks: Vitest, Jest, pytest, cargo-nextest. Use when setting up test infrastructure, migrating to a modern framework, or validating coverage config.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/laurigates/claude-plugins --skill configure-testsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
SKILL.md を表示中
SOC 職業分類に基づく
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-06-18T00:00:00.000Z" |
| reviewed | "2025-12-16T00:00:00.000Z" |
| description | Test frameworks: Vitest, Jest, pytest, cargo-nextest. Use when setting up test infrastructure, migrating to a modern framework, or validating coverage config. |
| allowed-tools | Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch |
| args | [--check-only] [--fix] [--framework <vitest|jest|pytest|nextest>] |
| argument-hint | [--check-only] [--fix] [--framework <vitest|jest|pytest|nextest>] |
| name | configure-tests |
Check and configure testing frameworks against best practices (Vitest, Jest, pytest, cargo-nextest).
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up testing infrastructure | Just running tests (use /test:run skill) |
| Checking test framework configuration | Tests already properly configured |
| Migrating to modern test frameworks (Vitest, pytest, nextest) | Writing individual tests (write tests directly) |
| Validating coverage configuration | Debugging failing tests (check test output) |
| Ensuring test best practices | Simple project with no testing needed |
find . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'Cargo.toml\'find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' -o -name '.nextest.toml' \)find . -maxdepth 1 -name 'pyproject.toml' -exec grep -c 'tool.pytest' {} +find . -maxdepth 2 -type d \( -name 'tests' -o -name '__tests__' -o -name 'test' \)find . -maxdepth 1 -name 'package.json' -exec grep -m5 -o '"test[^"]*"' {} +find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' \) -exec grep -l 'coverage' {} +find . -maxdepth 1 -name '.project-standards.yaml' -type fModern testing stack preferences:
Parse these from $ARGUMENTS:
| Flag | Description |
|---|---|
--check-only |
| Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--framework <framework> | Override framework detection (vitest, jest, pytest, nextest) |
CRITICAL: Before flagging outdated versions, verify latest releases:
Use WebSearch or WebFetch to verify current versions before reporting outdated frameworks.
Execute this testing framework compliance check:
Identify the project language and existing test framework:
| Indicator | Language | Detected Framework |
|---|---|---|
vitest.config.* | JavaScript/TypeScript | Vitest |
jest.config.* | JavaScript/TypeScript | Jest |
pyproject.toml [tool.pytest] | Python | pytest |
pytest.ini | Python | pytest |
Cargo.toml | Rust | cargo test |
.nextest.toml | Rust | cargo-nextest |
If --framework flag is provided, use that value instead.
Read the detected framework's configuration and check completeness. For each framework, verify:
Vitest:
vitest.config.ts or .js)globals: true configured for compatibilityenvironment set appropriately (jsdom, happy-dom, node)@vitest/coverage-v8 or @vitest/coverage-istanbulJest:
jest.config.js or .ts)testEnvironment configuredpytest:
pyproject.toml has [tool.pytest.ini_options] sectiontestpaths configuredaddopts includes useful flags (-v, --strict-markers)markers defined for test categorizationpytest-cov installedcargo-nextest:
.nextest.toml existsPrint a compliance report with:
If --check-only, stop here.
Install dependencies and create configuration using templates from REFERENCE.md:
Create standard test directory structure for the detected language. See directory structure patterns in REFERENCE.md.
Check for test commands in GitHub Actions workflows. If missing, add CI test commands using the CI templates from REFERENCE.md.
If migrating between frameworks (e.g., Jest to Vitest, unittest to pytest), follow the migration guide in REFERENCE.md.
Update .project-standards.yaml:
standards_version: "2025.1"
last_configured: "<timestamp>"
components:
tests: "2025.1"
tests_framework: "<vitest|jest|pytest|nextest>"
tests_coverage_threshold: 80
tests_ci_integrated: true
For detailed configuration templates, migration guides, CI/CD integration examples, and directory structure patterns, see REFERENCE.md.
| Context | Command |
|---|---|
| Detect test framework | find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' \) 2>/dev/null |
| Check coverage config | grep -l 'coverage' package.json pyproject.toml 2>/dev/null |
| List test files | find . \( -path '*/tests/*' -o -path '*/test/*' -o -name '*.test.*' -o -name '*.spec.*' \) 2>/dev/null | head -n 10 |
| Quick compliance check | /configure:tests --check-only |
| Auto-fix configuration | /configure:tests --fix |
/configure:coverage - Configure coverage thresholds and reporting/configure:all - Run all compliance checks/test:run - Universal test runner/test:setup - Comprehensive testing infrastructure setup