Agent skill
test
Run tests, analyze results, and produce a structured verdict.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/test-daemn256-workspace-repo-templ
SKILL.md
Test
The Test persona drives this workflow. Take test execution output, parse it into structured results, produce a clear verdict, and recommend next actions.
Prerequisites: Test output provided (pasted or from execution).
Phase 1: Parse Output
Extract structured data from raw test output.
Steps
- Identify the test framework from output format
- Extract total, passed, failed, skipped counts
- For failures, extract test name, location, error message
Phase 2: Produce Verdict
Classify the result and provide analysis.
Verdict Criteria
| Verdict | Criteria |
|---|---|
| PASS | All tests pass, no critical warnings |
| PARTIAL | Tests pass but with skipped tests or warnings |
| FAIL | One or more test failures |
Failure Analysis
For each failure:
- Identify the failing test name
- Extract the error message
- Note the file and line if available
- Analyze likely cause
- Suggest remediation approach
Common Failure Patterns
| Pattern | Likely Cause |
|---|---|
| Assertion failed | Logic error or incorrect expectation |
| Null reference | Missing setup or unexpected null |
| Timeout | Async issue or infinite loop |
| Connection refused | External dependency unavailable |
| Not found | Missing file, resource, or configuration |
Output
## Context Anchors
- **Issue:** #<number> - <title> (if applicable)
- **Suite:** <test suite name>
## Test Results
| Suite | Total | Pass | Fail | Skip |
| ----- | ----- | ---- | ---- | ---- |
| ... | ... | ... | ... | ... |
## Verdict: PASS | PARTIAL | FAIL
### Failures (if any)
| Test | Error | Location | Likely Cause |
| ------ | --------------- | ----------- | -------------- |
| <name> | <error message> | <file:line> | <likely cause> |
### Recommendations
- <next action>
## Next Step
<what comes next>
**Approval Required:** No
⛔ CHECKPOINT
STOP. Verify the verdict matches actual test output before reporting.
Critical: Never trust exit code alone. Parse and report actual counts.
Error Handling
| Error | Recovery |
|---|---|
| Unparseable output | Report what was understood, flag unknown sections |
| Mixed framework output | Process each framework section separately |
| No test output provided | Ask user to run tests and paste output |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?