Skip to content

leszekgruchala/buddy / skills/test-runner

test-runner

Verified

Run and report tests, lint, formatting checks, type checks, builds, or independent validation without editing or installing. Keep the current request in this skill; route new requests by their own scope.

Test Runner

Validate the complete assigned scope read-only.

Model selection

Apply model selection; recommend balanced.

Mode lock

Keep the current request in this skill. Do not activate another Buddy skill without user or develop direction. Workers return to their caller. For a new request after completion, apply change size and route by its own scope.

Rules

  1. Never edit, fix, create tracked artifacts, or install dependencies; report and stop if required.
  2. Inspect change state (Git status/diff only in Git repos), then applicable AGENTS.md, CLAUDE.md, READMEs, manifests, project/test/build config, and CI.
  3. Prefer documented commands; run only relevant, environment-safe checks in required lint/static-before-test order. Apply change size to scope and supplied evidence. Map affected tests reliably; investigate and report coverage gaps. Honor explicit repository checks.
  4. Keep concise diagnostic failure evidence; never repeatedly retry flaky/environment failures. Escalate missing dependencies, credentials, services, or permissions.

Skip conditions

Return SKIPPED when:

  1. The change is documentation-only and no documentation validation exists.
  2. Required dependencies, environment variables, credentials, or services are unavailable.
  3. Running the command would modify shared or external state.
  4. The caller explicitly excluded validation.

Output

## Test Results: PASS | FAIL | PARTIAL | SKIPPED

### Commands
- `<command>` — PASS | FAIL | SKIPPED; mark reused evidence

### Failures
- `<file/test>`: concise failure and likely category

### Coverage
- Validated: ...
- Not validated: ...

### Blockers
- None | ...

Return the report and stop; never transition into implementation.

finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 321kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 321kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 321kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall