Test Runner
Use when running repository tests and reporting concise, reproducible results in fast or full mode.
Install
npx skills add sandbaseai/workbuddy-skill --skill test-runnergit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/test-runner ~/.claude/skills/test-runnerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Runner Run tests with the smallest appropriate scope while preserving trustworthy evidence. Use this skill for local verification, change validation, and release checks; do not claim a test passed when it was skipped, flaky, or not actually run. ## Choose the mode and scope - **Fast:** the smallest deterministic suite that exercises the changed area and gives rapid feedback. - **Full:** the repository-defined unit, integration, end-to-end, static, and packaging checks required for a release or broad change. Determine the root and target from the user request, changed files, and repository conventions. If no target is specified, use the repository root and fast mode unless the change or release gate requires full mode. Do not silently expand into unrelated repositories or production systems. ## Select commands safely Prefer, in order: 1. `PROJECT.md` or equivalent contributor documentation; 2. repository entry points such as `make`, `task`, `just`, package scripts, or checked-in CI commands; 3. the language/framework test runner only when the repository has no clearer entry point. Inspect the relevant script before running it. Preserve required environment setup, fixtures, seed data, and working directory. Never install packages, contact external services, mutate production data, or run destructive migrations merely to guess how a test works; stop and report the missing prerequisite when authorization or safety is unclear.
Details
- Skill name
test-runner- Repository
- sandbaseai/workbuddy-skill
- Path
skills/test-runner/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Test Runner skill do?
Use when running repository tests and reporting concise, reproducible results in fast or full mode.
How do I install the Test Runner skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill test-runner. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Runner popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Tight Bug Loop
9sandbaseai/workbuddy-skill
Use when diagnosing a hard bug or performance regression and a fast, deterministic, symptom-specific feedback loop is needed before forming or testing hypotheses.
Test Driven Development
9sandbaseai/workbuddy-skill
Use when implementing a feature, bug fix, refactor, or behavior change and a regression-safe test-first workflow is appropriate.
Webapp Testing
9sandbaseai/workbuddy-skill
Use when testing or debugging an authorized local web application with Playwright, including user flows, responsive behavior, screenshots, console logs, and network evidence.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.