test-run
Universal test runner auto-detecting pytest, vitest, jest, cargo, go test. Use when running tests, targeting a file/pattern, running with coverage, or watch-mode dev loops.
What this skill does
## When to Use This Skill | Use this skill when... | Use test-quick instead when... | |---|---| | Running tests with auto-detected framework (pytest, vitest, jest, cargo, go) | You only want fast unit tests for sub-30s feedback | | Running a specific file or pattern with full framework defaults | Iterating on a single failing spec (use test-focus) | | Generating coverage in the standard run | Running the full pyramid before a PR (use test-full) | | Starting a watch-mode dev loop across the project | Triaging existing test results (use test-analyze) | ## Context - Project indicators: !`find . -maxdepth 1 \( -name 'pyproject.toml' -o -name 'package.json' -o -name 'Cargo.toml' -o -name 'go.mod' \)` - Test directories: !`find . -maxdepth 1 -type d \( -name 'tests' -o -name 'test' -o -name '__tests__' -o -name 'spec' \)` - Package.json test script: !`grep -A2 '"test"' package.json` - Pytest config: !`grep -A5 '\[tool.pytest' pyproject.toml` ## Parameters - `$1`: Optional test pattern or specific test file/directory - `--coverage`: Enable coverage reporting - `--watch`: Run tests in watch mode ## Your task **Delegate this task to the `test-runner` agent.** Use the Agent tool with `subagent_type: test-runner` to run tests with the appropriate framework. Pass all the context gathered above and the parsed parameters to the agent. The test-runner agent should: 1. **Detect project type and test framework**: - Python: pytest, unittest, nose - Node.js: vitest, jest, mocha - Rust: cargo test - Go: go test 2. **Run appropriate test command**: - Apply test pattern if provided - Enable coverage if requested - Enable watch mode if requested 3. **Analyze results**: - Parse test output for pass/fail counts - Identify failing tests with clear error messages - Extract coverage metrics if available 4. **Provide concise summary**: ``` Tests: [PASS|FAIL] Passed: X | Failed: Y | Duration: Zs Failures (if any): - test_name: Brief error (file:line) Coverage: XX% (if requested) ``` 5. **Suggest next actions**: - If failures: specific fix recommendations - If coverage gaps: areas needing tests - If slow: optimization suggestions Provide the agent with: - All context from the section above - The parsed parameters (pattern, --coverage, --watch) - Any specific test configuration detected The agent has expertise in: - Multi-framework test execution - Test failure analysis and debugging - Coverage reporting and gap identification - Tiered test execution (unit, integration, e2e)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.