/cli-anything-test
Run CLI-Anything harness tests against the real backend and update TEST.md with passing results
> /plugin marketplace add HKUDS/CLI-Anything > /plugin install cli-anything@cli-anything
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/cli-anything-test
Context preview
What this command does when you run it.
Run CLI-Anything harness tests against the real backend and update TEST.md with passing results
Command definition
cli-anything-test.mdname: cli-anything-test
description: Run CLI-Anything harness tests against the real backend and update TEST.md with passing results
cli-anything-test Command
Run and document tests for an existing harness.
**Target software**: local path argument (required).
CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)
1. Read `~/.cursor/cli-anything-generator.root` / `%USERPROFILE%\.cursor\cli-anything-generator.root` 2. Else install dir `PLUGIN_ROOT.txt` / default `.../plugins/local/cli-anything` 3. Read `{PLUGIN_ROOT}/references/HARNESS.md` and `{PLUGIN_ROOT}/references/commands/test.md` via absolute paths
Cursor Tool Bindings
| Cursor tool | Role | |-------------|------| | Shell | `pytest`, installed `cli-anything-<software>`, environment checks | | Read / Grep | Locate tests, parse failures, update TEST.md | | Write / StrReplace | Fix tests or harness bugs uncovered by failures |
Phase Gates and Resume (hard gate)
Progress: `{software-root}/agent-harness/.cli-anything-progress.json` with `"mode": "test"`.
- Track unit / e2e / installed-CLI / TEST.md update steps; do not skip ahead without marking completion.
- Resume if interrupted; only append **passing** evidence to `TEST.md`.
- Prefer `CLI_ANYTHING_FORCE_INSTALLED=1` for release-style installed-command checks when documented by HARNESS / test command.
Test checklist
- Run unit + E2E suites
- Verify installed `cli-anything-<software>` via subprocess / `_resolve_cli`
- Update `TEST.md` only with passing results
What This Command Does
Follow `{PLUGIN_ROOT}/references/commands/test.md`.
Read more
name: cli-anything-test description: Run CLI-Anything harness tests against the real backend and update TEST.md with passing results
cli-anything-test Command
Run and document tests for an existing harness.
**Target software**: local path argument (required).
CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)
1. Read `~/.cursor/cli-anything-generator.root` / `%USERPROFILE%\.cursor\cli-anything-generator.root` 2. Else install dir `PLUGIN_ROOT.txt` / default `.../plugins/local/cli-anything` 3. Read `{PLUGIN_ROOT}/references/HARNESS.md` and `{PLUGIN_ROOT}/references/commands/test.md` via absolute paths
Cursor Tool Bindings
| Cursor tool | Role | |-------------|------| | Shell | `pytest`, installed `cli-anything-<software>`, environment checks | | Read / Grep | Locate tests, parse failures, update TEST.md | | Write / StrReplace | Fix tests or harness bugs uncovered by failures |
Phase Gates and Resume (hard gate)
Progress: `{software-root}/agent-harness/.cli-anything-progress.json` with `"mode": "test"`.
- Track unit / e2e / installed-CLI / TEST.md update steps; do not skip ahead without marking completion.
- Resume if interrupted; only append **passing** evidence to `TEST.md`.
- Prefer `CLI_ANYTHING_FORCE_INSTALLED=1` for release-style installed-command checks when documented by HARNESS / test command.
Test checklist
- Run unit + E2E suites
- Verify installed `cli-anything-<software>` via subprocess / `_resolve_cli`
- Update `TEST.md` only with passing results
What This Command Does
Follow `{PLUGIN_ROOT}/references/commands/test.md`.
"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/
Repo: HKUDS/CLI-Anything
Other commands on cli-anything.
refine
Refine an existing CLI harness to improve coverage of the software's functions and usage patterns.

