typescript-plugin/skills/bun-test/SKILL.md
Bun test runner with compact agent-friendly output. Use when running bun tests, targeting a pattern, collecting --coverage, watching, or emitting JUnit XML for CI.
npx skillsauth add laurigates/claude-plugins bun-testInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run tests using Bun's built-in test runner with optimized output.
| Scenario | Use this skill | Alternative |
|----------|---------------|-------------|
| Quickly running tests with compact output | Yes | N/A |
| Running a specific test file or pattern | Yes | N/A |
| Running tests with coverage | Yes | N/A |
| Configuring test runner options in detail | No - use bun-development | Full test configuration guidance |
| Debugging failing tests interactively | No - use typescript-debugging | Inspector-based debugging |
pattern (optional): Test file or name pattern--coverage: Enable code coverage reporting--bail: Stop on first failure--watch: Watch mode for developmentQuick feedback (default for agentic use):
bun test --dots --bail=1 $PATTERN
With coverage:
bun test --dots --coverage $PATTERN
Watch mode:
bun test --watch $PATTERN
CI mode (JUnit output):
bun test --reporter=junit --reporter-outfile=junit.xml $PATTERN
| Symbol | Meaning |
|--------|---------|
| . | Test passed |
| F | Test failed |
| S | Test skipped |
| Context | Command |
|---------|---------|
| Quick test | bun test --dots --bail=1 |
| Filtered test | bun test --dots --bail=1 -t "pattern" |
| With coverage | bun test --dots --coverage |
| CI output | bun test --reporter=junit --reporter-outfile=junit.xml |
| Watch mode | bun test --watch |
testing
Verify accumulated bug claims at upstream HEAD and dedup against trackers before filing issues. Use when filing upstream reports from backlogs, audit docs, or git-history findings.
documentation
Gate outward-bound text (upstream issues, docs, PR bodies) through isolated haiku fresh-reader critique before publishing. Use when an artifact must survive a reader with zero project context.
tools
Suggest improvements to SKILL.md content, descriptions, or tool config from eval results. Use when raising pass rates, fixing triggering, or iterating on a skill after evaluation.
tools
deadbranch CLI for stale-branch cleanup — dry-run preview, TUI or non-interactive delete, protects main/develop/WIP. Use when asked to clean up branches, prune branches, or remove stale branches.