Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From cli-anything
Runs pytest tests for CLI harness on local path or GitHub repo, verifies CLI resolution, and updates TEST.md with results if all pass.
npx claudepluginhub hkuds/cli-anything --plugin cli-anythingHow this command is triggered — by the user, by Claude, or both
Slash command
/cli-anything:testThe summary Claude sees in its command listing — used to decide when to auto-load this command
# cli-anything:test Command Run tests for a CLI harness and update TEST.md with results. ## CRITICAL: Read HARNESS.md First **Before running tests, read `./HARNESS.md`.** It defines the test standards, expected structure, and what constitutes a passing test suite. ## Usage ## Arguments - `<software-path-or-repo>` - **Required.** Either: - A **local path** to the software source code (e.g., `/home/user/gimp`, `./blender`) - A **GitHub repository URL** (e.g., `https://github.com/GNOME/gimp`, `github.com/blender/blender`) If a GitHub URL is provided, the agent clones the repo lo...
/testRuns full pytest suite (unit, E2E, subprocess) for cli-anything-web CLI at <app-path>, verifies auth, parses results, updates TEST.md, analyzes failures.
/testRuns tests using auto-detected command (npm test, pytest, cargo test, go test, etc.) or provided one, analyzes failures with root causes and fix suggestions, reports summary with pass/fail counts.
/testRuns a TDD workflow: write failing tests, implement code, and verify. For bug fixes, uses the Prove-It pattern to reproduce, fix, and confirm.
/testExecutes unit, integration, or e2e tests with coverage analysis, quality metrics, failure diagnostics, and optional watch mode or auto-fixes.
/testGenerates test strategy overview, unit and integration test code, coverage analysis, execution plan, and maintenance roadmap for a specified component or feature.
/testLaunches Chrome for manual UI testing at given URL, monitors console errors during interaction, generates report with screenshots and logs on completion.
Share bugs, ideas, or general feedback.
Run tests for a CLI harness and update TEST.md with results.
Before running tests, read ./HARNESS.md. It defines the test standards, expected structure, and what constitutes a passing test suite.
/cli-anything:test <software-path-or-repo>
<software-path-or-repo> - Required. Either:
/home/user/gimp, ./blender)https://github.com/GNOME/gimp, github.com/blender/blender)If a GitHub URL is provided, the agent clones the repo locally first, then works on the local copy.
The software name is derived from the directory name. The agent locates the CLI harness at /root/cli-anything/<software-name>/agent-harness/.
-v -s --tb=short[_resolve_cli] Using installed command: appears in outputThe command appends to TEST.md:
## Test Results
Last run: 2024-03-05 14:30:00
[full pytest -v --tb=no output]
**Summary**: 103 passed in 3.05s
# Run all tests for GIMP CLI
/cli-anything:test /home/user/gimp
# Run tests for Blender from GitHub
/cli-anything:test https://github.com/blender/blender
[_resolve_cli] output confirms installed command pathIf tests fail: