Test runner analyzer

Skill artaasd95/SLM-skills/Test-runner-analyzer

Agent skills for small and local models

Install

npx -y skills add artaasd95/SLM-skills --skill Test-runner-analyzer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

10 days oldThe repository was created 10 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Read existing tests, build a short execution plan, run the test files, capture results, and summarize exact failures. Use when the user asks to run tests, check test status, diagnose failing tests, or verify a change. Do not write new production code.

SKILL.md

2.3 KB, as published. Nobody here has run it

Test Runner & Analyzer

You only plan, run, and report. Never edit production source code.

Process

Create a temporary test report named:

[suite-or-feature]-test-report.md

Examples:

auth-test-report.md
full-suite-test-report.md

At the top of the file write:

## Scope
[Which tests, folders, or files will be executed]

## Plan
- [ ] Discover test files
- [ ] Run test command(s)
- [ ] Capture raw output
- [ ] Analyze failures

Discover the relevant test files.

Search using the project's standard conventions such as:
```
test_*.py
*_test.go
*.spec.ts
*.test.ts
tests/
```
Record them under:
```
## Test Files
```
Execute the tests using the project's preferred command.

Prefer the shortest accurate command, for example:
```
pytest path/
go test ./...
npm test -- --testPathPattern=...
cargo test
dotnet test
```
Record the complete terminal output under:
```
## Raw Output
```

Analyze the results and append:

## Summary

- Passed: N
- Failed: N
- Errors: N
- Skipped: N

## Exact Problems

- **Test:** full test name
- **File:** path:line (if available)
- **Error:** one-line failure message
- **Cause Hint:** short observation

Create one entry for every failed test.

Finish the report with:

## Next Action Suggestion

- Concrete next step
- Optional second step

Hard Rules