test-quick
/test-quick
Unit tier only — skips slow, integration, and E2E tests for sub-30s feedback. Use when checking units after a change, running tests affected since the last commit, or unit watch mode.
- Author
- laurigates ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Unit tier only — skips slow, integration, and E2E tests for sub-30s feedback. Use when checking units after a change, running tests affected since the last commit, or unit watch mode.
Arguments
/test-quick [path] [--watch] [--affected]
Original author description
Unit tier only — skips slow, integration, and E2E tests for sub-30s feedback. Use when checking units after a change, running tests affected since the last commit, or unit watch mode.
How it works
- When to Use This Skill
- Context
- Parameters
- Your task
SKILL.md preview
---
created: 2025-12-16
modified: 2026-09-05
reviewed: 2026-04-25
allowed-tools: Task, TodoWrite
args: "[path] [--watch] [--affected]"
argument-hint: "[path] [--watch] [--affected]"
description: "Unit tier only — skips slow, integration, and E2E tests for sub-30s feedback. Use when checking units after a change, running tests affected since the last commit, or unit watch mode."
name: test-quick
---
## 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 . -path '*/.pytest_cache/v/cache/*' -maxdepth 4 -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: testing-plugin:test-runner` to run fast unit tests only. Pass all the context gathered in [Context](#context) 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 [Context](#context)
- 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
Versions
The database has no other skills named test-quick.
Database snapshot: 13.11.2026 · package version e5b973245135 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100test-unit
Write unit and integration tests for a named module or change. Use when "write unit tests" or "add tests for this function". Coverage plan → plan-test-coverage. Mutation score → test-mutation. Browser check → test-playwright. - 100test-full
Every tier in pyramid order — unit, then integration, then E2E. Use when running all tests before a PR or commit, or generating a coverage report. - 100testing
Creates and manages unit and integration tests: detects the test framework, follows project conventions, runs the fix-loop. Use when the user mentions "write tests", "unit tests", "integration tests", "test coverage", "tests missing", "TDD", or after implementation when tests… - 100write-tests
Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests". - 100backend-test
Generate backend tests (unit, integration, mocks) for existing code. Auto-invoke when user says "write test for", "add test", "test this", or "create test". - 100cargo-test
Expert Cargo test assistance covering Rust unit tests, integration tests, and benchmarks. Use when running `cargo test`, writing unit tests in Rust, or debugging test failures.