| name | auto-tester |
| description | Runs validation tests on code, skills, or outputs after changes. Use after i mplementations or when user says run tests, auto test, validate changes. Tri ggers: run tests, auto test, validate changes. Use when the user needs this capability.
|
| version | 1.1.0 |
| author | Stijnman |
| license | MIT |
| metadata | {"grok":{"tags":["run tests","auto test","validate changes","check tests"],"related_skills":["goal-verifier","self-healing-error-recovery","hyper-skill-tester"]}} |
| compatibility | Grok agent; optional MCP and shell access |
Auto Tester
When to Use
- User says run tests or task matches this capability
- User says auto test or task matches this capability
- User says validate changes or task matches this capability
- User says check tests or task matches this capability
Workflow
- Detect project type (Python, Node, skill-only).
- Run appropriate test command (pytest, npm test, or skill checklist).
- Parse results; classify pass/fail/flaky.
- On fail: invoke self-healing-error-recovery or report with fix hints.
Integrations
goal-verifierself-healing-error-recoveryhyper-skill-tester
Error Handling
| Failure | Response |
|---|
| No test suite | Run smoke checks: import, lint, dry-run. |
Gotchas
- Never skip tests before marking goal-verifier complete.
Example
Input: User request matching triggers above.
Output: Structured result per workflow with integrations invoked as needed.
