test-quick
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.
Works with
---
name: test-quick
description: 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.
license: MIT
---
## 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: 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 parallelizationMore Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

