Slash Command

/SKILL

Runs narrowest relevant tests for changed files or requests, using commands like `bun test <file>` for TypeScript, `gradlew test` for Android, `swift-test.sh` for iOS; summarizes failures.

Typescript

Bun

npx claudepluginhub kaeawc/auto-mobile --plugin auto-mobile

Details

Namespacetest/

Prompt Preview

# Run Tests

Use the smallest test command that answers the user’s question.

- This skill is test-focused.
- Prefer `validate` when lint, build, formatting, or other non-test checks are part of the request.

## Workflow

1. Determine the scope from the changed files or the user request.
2. Prefer targeted tests before full suites.
3. For TypeScript, use `bun test <file>` or `bun test --bail` before `bun test` when narrowing failures.
4. For Android or iOS, run only the relevant platform test command.
5. Save verbose logs to `scratch/` when needed and summarize failures with file names and ...

Command Content

Other plugins with /SKILL

/test

Executes intelligent tests based on PR changes or patterns/modifiers, runs them via ./run_tests.sh, analyzes/fixes results, and verifies GitHub CI status.

claude-commands

/test

Runs project test suite by auto-detecting type (Python, Node.js, Java, .NET, Go, Rust) and executing tests (pytest, npm test, mvn test, etc.). Reports pass/fail, details failures, suggests fixes.

4 tools

cc-best

/SKILL

512

Configures Git user identity and project commit scopes: verifies name/email, initializes git-agent, validates scopes from .git-agent/config.yml, generates .claude/git.local.md.

haiku7 tools

git

/SKILL

512

Launches isolated code-context researcher agent to fetch repo/library context via DeepWiki, Context7, Exa, git clone, or all methods. Accepts repo URL/name and optional --method flag.

code-context

/SKILL

512

Creates a GitHub pull request with automated quality validation, security scanning, issue linking, and compliance checks. Accepts optional description or issue reference.

3 tools

github

/SKILL

512

Creates executable implementation plans from design folders, decomposing specs into granular tasks via phased loop with user validation and git commit.

3 tools

superpowers

Stats

Stars34

Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Run Tests Use the smallest test command that answers the user’s question. - This skill is test-focused. - Prefer `validate` when lint, build, formatting, or other non-test checks are part of the request. ## Workflow 1. Determine the scope from the changed files or the user request. 2. Prefer targeted tests before full suites. 3. For TypeScript, use `bun test <file>` or `bun test --bail` before `bun test` when narrowing failures. 4. For Android or iOS, run only the relevant platform test command. 5. Save verbose logs to `scratch/` when needed and summarize failures with file names and ...

Run Tests

Use the smallest test command that answers the user’s question.

This skill is test-focused.

Prefer validate when lint, build, formatting, or other non-test checks are part of the request.

Workflow

Determine the scope from the changed files or the user request.

Prefer targeted tests before full suites.

For TypeScript, use bun test <file> or bun test --bail before bun test when narrowing failures.

For Android or iOS, run only the relevant platform test command.

Save verbose logs to scratch/ when needed and summarize failures with file names and root causes.

Repo Validation Mapping

TypeScript all tests: bun test

Single TypeScript file: bun test <file>

Timing budget check: bash scripts/validate-bun-test-timings.sh

Android: (cd android && ./gradlew test) or a narrower task

iOS Swift package tests: bash scripts/ios/swift-test.sh

Local component or integration flows: prefer a purpose-built script in scripts/

Test Quality Rules

Keep unit tests fast and deterministic.

Use interfaces, fakes, and fake timers when adding or fixing tests.

Do not accept a failing test as an allowable outcome.

Run Tests

Use the smallest test command that answers the user’s question.

This skill is test-focused.
Prefer validate when lint, build, formatting, or other non-test checks are part of the request.

Workflow

Determine the scope from the changed files or the user request.
Prefer targeted tests before full suites.
For TypeScript, use bun test <file> or bun test --bail before bun test when narrowing failures.
For Android or iOS, run only the relevant platform test command.
Save verbose logs to scratch/ when needed and summarize failures with file names and root causes.

Repo Validation Mapping

TypeScript all tests: bun test
Single TypeScript file: bun test <file>
Timing budget check: bash scripts/validate-bun-test-timings.sh
Android: (cd android && ./gradlew test) or a narrower task
iOS Swift package tests: bash scripts/ios/swift-test.sh
Local component or integration flows: prefer a purpose-built script in scripts/

Test Quality Rules

Keep unit tests fast and deterministic.
Use interfaces, fakes, and fake timers when adding or fixing tests.
Do not accept a failing test as an allowable outcome.