Skip to main content
configure-tests Test frameworks: Vitest, Jest, pytest, cargo-nextest. Use when setting up test infrastructure, migrating to a modern framework, or validating coverage config.
Zur Installation springen Skills Marktplatz Entdecken und erkunden Sie KI-Skills, die von der Community erstellt wurden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Prompt-Details anzeigen Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-testsDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
ZIP herunterladen Herunterladen... Verwandte Berufe SOC
Basierend auf der SOC-Berufsklassifikation
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
/configure:tests
Check and configure testing frameworks against best practices (Vitest, Jest, pytest, cargo-nextest).
When to Use This Skill
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
Context
Package.json: !find . -maxdepth 1 -name \'package.json\'
Pyproject.toml: !find . -maxdepth 1 -name \'pyproject.toml\'
Cargo.toml: !find . -maxdepth 1 -name \'Cargo.toml\'
Test config files: !find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' -o -name '.nextest.toml' \)
Pytest in pyproject: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep -c 'tool.pytest' {} +
Test directories: !find . -maxdepth 2 -type d \( -name 'tests' -o -name '__tests__' -o -name 'test' \)
Test scripts in package.json: !find . -maxdepth 1 -name 'package.json' -exec grep -m5 -o '"test[^"]*"' {} +
Coverage config: !find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' \) -exec grep -l 'coverage' {} +
Project standards: !find . -maxdepth 1 -name '.project-standards.yaml' -type f
Modern testing stack preferences:
JavaScript/TypeScript : Vitest (preferred) or JestPython : pytest with pytest-covRust : cargo-nextest for improved performance
Parameters
Parse these from $ARGUMENTS:
Flag Description --check-only
Report status without offering fixes
--fixApply all fixes automatically without prompting
--framework <framework>Override framework detection (vitest, jest, pytest, nextest)
Version Checking CRITICAL : Before flagging outdated versions, verify latest releases:
Use WebSearch or WebFetch to verify current versions before reporting outdated frameworks.
Execution Execute this testing framework compliance check:
Step 1: Detect framework 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.iniPython pytest Cargo.tomlRust cargo test .nextest.tomlRust cargo-nextest
If --framework flag is provided, use that value instead.
Step 2: Analyze current state Read the detected framework's configuration and check completeness. For each framework, verify:
Config file exists (vitest.config.ts or .js)
globals: true configured for compatibilityenvironment set appropriately (jsdom, happy-dom, node)Coverage configured with @vitest/coverage-v8 or @vitest/coverage-istanbul
Watch mode exclusions configured
Config file exists (jest.config.js or .ts)
testEnvironment configuredCoverage configuration present
Transform configured for TypeScript/JSX
Module path aliases configured
pyproject.toml has [tool.pytest.ini_options] sectiontestpaths configuredaddopts includes useful flags (-v, --strict-markers)markers defined for test categorizationpytest-cov installed
.nextest.toml existsProfile configurations (default, ci)
Retry policy configured
Test groups defined if needed
Step 3: Report results Print a compliance report with:
Detected framework and version
Configuration check results for each item
Test organization (unit/integration/e2e directories)
Package scripts status (test, test:watch, test:coverage)
Overall issue count and recommendations
If --check-only, stop here.
Step 4: Apply fixes (if --fix or user confirms) Install dependencies and create configuration using templates from REFERENCE.md :
Missing config : Create framework config file from templateMissing dependencies : Install required packagesMissing coverage : Add coverage configuration with 80% thresholdMissing scripts : Add test scripts to package.jsonMissing test directories : Create standard test directory structure
Step 5: Set up test organization Create standard test directory structure for the detected language. See directory structure patterns in REFERENCE.md .
Step 6: Configure CI/CD integration Check for test commands in GitHub Actions workflows. If missing, add CI test commands using the CI templates from REFERENCE.md .
Step 7: Handle migration (if upgrading) If migrating between frameworks (e.g., Jest to Vitest, unittest to pytest), follow the migration guide in REFERENCE.md .
Step 8: Update standards tracking 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 .
Agentic Optimizations Context Command Detect test framework find . -maxdepth 1 \( -name 'vitest.config.*' -o -name 'jest.config.*' -o -name 'pytest.ini' \) 2>/dev/nullCheck coverage config grep -l 'coverage' package.json pyproject.toml 2>/dev/nullList test files find . \( -path '*/tests/*' -o -path '*/test/*' -o -name '*.test.*' -o -name '*.spec.*' \) 2>/dev/null | head -n 10Quick compliance check /configure:tests --check-onlyAuto-fix configuration /configure:tests --fix
Error Handling
No package.json found : Cannot configure JS/TS tests, skip or errorConflicting frameworks : Warn about multiple test configs, require manual resolutionMissing dependencies : Offer to install required packagesInvalid config syntax : Report parse error, offer to replace with template
See Also
/configure:coverage - Configure coverage thresholds and reporting/configure:all - Run all compliance checks/test:run - Universal test runner/test:setup - Comprehensive testing infrastructure setupVitest documentation : https://vitest.dev pytest documentation : https://docs.pytest.org cargo-nextest documentation : https://nexte.st Mehr aus diesem Repository 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.
