How do I install the Test skill?

Run npx skillmds@latest add phel-lang/test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Test skill do?

Run tests with smart filtering by scope, class, or file path It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

phel-lang (@phel-lang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test by phel-lang — Agent Skill

Name: Test
Author: phel-lang

File contents

Quick Test Runner

Scope mapping

Run the minimum scope for the changed files. Prefer narrow over broad.

Changed	Command	Notes
`src/php/**`	`composer test-compiler`	PHPUnit unit + integration
`src/phel/**`	`composer test-core`	Phel core tests
`src/php/Compiler/**`	`composer test-compiler`	Full compiler suite
Single PHP module	`./vendor/bin/phpunit --filter=ModuleName`	Fastest for focused work
Single Phel file	`./bin/phel test tests/phel/<file>`	Target a specific test
Any `.php` style change	`composer test-quality`	Static analysis only
Mixed PHP + Phel	`composer test`	Run everything

Available composer scripts:

composer test              # All tests (quality + compiler + core)
composer test-quality      # Static analysis: cs-fixer, psalm, phpstan, rector
composer test-compiler     # PHPUnit unit + integration tests
composer test-core         # Phel core tests (./bin/phel test)
composer fix               # Auto-fix: rector + cs-fixer

Instructions

If $ARGUMENTS is empty or all:
```
composer test
```
If $ARGUMENTS is a known scope:
- quality → composer test-quality
- compiler → composer test-compiler
- core → composer test-core
- quick → composer test-compiler && composer test-core (skip static analysis)
- bench → composer phpbench
If $ARGUMENTS looks like a test class or method name:
```
./vendor/bin/phpunit --filter "$ARGUMENTS"
```

If $ARGUMENTS looks like a file path:

./vendor/bin/phpunit "$ARGUMENTS"
# or for Phel tests:
./bin/phel test "$ARGUMENTS"

Report results clearly with pass/fail count.

---name: testdescription: Run tests with smart filtering by scope, class, or file path---# Quick Test Runner## Scope mappingRun the **minimum** scope for the changed files. Prefer narrow over broad.| Changed | Command | Notes ||--------------------------|-----------------------------------------------|------------------------------------|| `src/php/**` | `composer test-compiler` | PHPUnit unit + integration || `src/phel/**` | `composer test-core` | Phel core tests || `src/php/Compiler/**` | `composer test-compiler` | Full compiler suite || Single PHP module | `./vendor/bin/phpunit --filter=ModuleName` | Fastest for focused work || Single Phel file | `./bin/phel test tests/phel/<file>` | Target a specific test || Any `.php` style change | `composer test-quality` | Static analysis only || Mixed PHP + Phel | `composer test` | Run everything |Available `composer` scripts:```bashcomposer test # All tests (quality + compiler + core)composer test-quality # Static analysis: cs-fixer, psalm, phpstan, rectorcomposer test-compiler # PHPUnit unit + integration testscomposer test-core # Phel core tests (./bin/phel test)composer fix # Auto-fix: rector + cs-fixer```## Instructions1. If `$ARGUMENTS` is empty or `all`: ```bash composer test ```2. If `$ARGUMENTS` is a known scope: - `quality` → `composer test-quality` - `compiler` → `composer test-compiler` - `core` → `composer test-core` - `quick` → `composer test-compiler && composer test-core` (skip static analysis) - `bench` → `composer phpbench`3. If `$ARGUMENTS` looks like a test class or method name: ```bash ./vendor/bin/phpunit --filter "$ARGUMENTS" ```4. If `$ARGUMENTS` looks like a file path: ```bash ./vendor/bin/phpunit "$ARGUMENTS" # or for Phel tests: ./bin/phel test "$ARGUMENTS" ```5. Report results clearly with pass/fail count.

Frequently asked questions

Test

File contents

Quick Test Runner

Scope mapping

Instructions

Related skills

Frequently asked questions

How do I install the Test skill?

What does the Test skill do?

Is Test safe to use?

Which AI agents work with Test?

Is Test free to use?

Who published Test?