Menu
Use when running workspace tests, choosing a test command, or summarizing results before handoff to debugger.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when running workspace tests, choosing a test command, or summarizing results before handoff to debugger.
Use when: running pre-commit or pre-push CI-equivalent checks in any workspace — discovers workflow commands with Cursor tools, filters for local executability, scopes to staged changes, and runs checks cheapest-first.
Use when the user wants to install or customize cursorAssistant in the current project (GitHub install or configure).
Use when: running pre-commit or pre-push CI-equivalent checks in any workspace — discovers workflow commands with Cursor tools, filters for local executability, scopes to staged changes, and runs checks cheapest-first.
Use when: discovering package manifests, assessing dependency health, finding replacements, or confirming import usage before removal — discovery only; mutating installs are handled by the deps agent.
Use before proposing cursorAssistant setup, update, or repair — inspect lockfile and managed file drift.
| name | testing |
| description | Use when running workspace tests, choosing a test command, or summarizing results before handoff to debugger. |
| version | 1.1 |
| license | MIT |
Run tests through the project's declared command. Prefer Shell; use pack MCP tools only when installed.
debuggertddCycle, etc.){{TEST_COMMAND}} when present; otherwise Glob / Read package.json, pyproject.toml, Makefile, or README for the canonical test command.debugger with logs.When the tdd pack is installed, workspaceTesting or tddTestRunner may appear in .cursor/mcp.json. Use them for structured runner discovery; otherwise stay on Shell.
debugger with logs