/test

> Run test suite, report coverage, flag failures with diagnostics.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Run test suite, report coverage, flag failures with diagnostics.

Teams using /test should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/test/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/development/test/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/test/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /test Compares

Feature / Agent	/test	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Run test suite, report coverage, flag failures with diagnostics.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /test

> Run test suite, report coverage, flag failures with diagnostics.

## Usage
```
/test [path] [--watch] [--coverage] [--filter <pattern>] [--fail-fast] [--seed <n>]
```

## What It Does
Detects the test framework, runs the suite, collects coverage data, identifies failures with root cause analysis, and reports results in a structured format. Diagnoses each failure by reading both the test and the code under test.

## Implementation
1. **Detect test framework** from project config (ExUnit, Vitest, Jest, Go test, pytest).
2. **Prepare environment** -- ensure test DB exists, migrations run, test deps installed.
3. **Run tests** with appropriate flags. Capture stdout, stderr, exit code, duration.
4. **Parse results** -- total, passed, failed, skipped. Per-failure: file, line, assertion, expected vs actual.
5. **Diagnose failures** -- read test source + code under test, identify root cause, suggest fix.
6. **Coverage analysis** (if `--coverage`) -- identify files below 80%, list uncovered branches, suggest tests to write.

## Examples
```bash
# Run full test suite
/test

# Run specific file with coverage
/test test/engine_test.exs --coverage

# Run tests matching pattern
/test --filter "user authentication"

# Watch mode during development
/test --watch --fail-fast
```

## Command