test-quick

Included with Lifetime

$97 forever

Run fast unit tests only, skip slow/integration/E2E. Use when checking units after a change, running affected tests since last commit, watch mode TDD, or sub-30s feedback.

Code Review

What this skill does


## When to Use This Skill

| Use this skill when... | Use test-full instead when... |
|---|---|
| Running unit tests only for sub-30s feedback | Running the full pyramid (unit + integration + E2E) before a PR |
| Restricting to tests affected by recent changes (`--affected`) | Generating coverage or HTML reports across all tiers |
| Running watch-mode TDD on unit tests | Iterating on a single failing file (use test-focus) |
| Confirming nothing broke after a small refactor | Triaging test results from a prior run (use test-analyze) |

## Context

- Project type: !`find . -maxdepth 1 \( -name 'pyproject.toml' -o -name 'package.json' -o -name 'Cargo.toml' -o -name 'go.mod' \)`
- Test directories: !`find . -maxdepth 2 -type d \( -path '*/tests/unit' -o -path '*/test/unit' -o -path '*/__tests__/unit' \)`
- Last test run: !`find .pytest_cache/v/cache -maxdepth 1 -name 'lastfailed'`

## Parameters

- `$1`: Optional path or test pattern
- `--watch`: Enable watch mode for continuous feedback
- `--affected`: Only run tests for files changed since last commit

## Your task

**Delegate this task to the `test-runner` agent.**

Use the Agent tool with `subagent_type: test-runner` to run fast unit tests only. Pass all the context gathered above and specify **Tier 1 (unit tests)** execution.

The test-runner agent should:

1. **Run unit tests only** (target < 30s):
   - Exclude slow, integration, and E2E tests
   - Use appropriate markers/flags for the framework:
     - pytest: `-m "not slow and not integration and not e2e"`
     - vitest: `--exclude="**/e2e/**" --exclude="**/integration/**"`
     - cargo: `--lib`
     - go: `-short`

2. **Apply options**:
   - If `--watch`: Enable continuous test execution
   - If `--affected`: Only test changed files

3. **Fail fast**: Stop on first failure (`-x` or `--bail`)

4. **Provide concise output**:
   ```
   Unit Tests: [PASS|FAIL]
   Passed: X | Failed: Y | Duration: Zs

   Failures (if any):
   - test_name: Brief error (file:line)

   Rerun failed: [command]
   ```

5. **Post-action guidance**:
   - If all pass: Ready for continued development
   - If failures: Fix before proceeding (fail fast principle)
   - If > 30s: Suggest `/test:consult` for optimization

Provide the agent with:
- All context from the section above
- The parsed parameters
- **Explicit instruction**: Tier 1 only, skip slow tests

The agent has expertise in:
- Tiered test execution
- Fast feedback loops
- Test isolation and parallelization

Files: 1

Size: 2.8 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/laurigates/claude-plugins/tree/main/testing-plugin/skills/test-quick

Related in Code Review

gstack

Included

Fast 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)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal 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.

Code Reviewscripts

interview-master

Included

This 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.

Code Reviewscripts

fix-issue

Included

Fixes 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.

Code Reviewscripts

sf-apex

Included

Generates 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.

Code Reviewscripts

swift-development

Included

Comprehensive 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.

Code Reviewscripts