test-report
Show cached test status without re-running. Use when checking test health, standup status, coverage summary, history, or identifying flaky tests from recent runs.
Works with
--- name: test-report description: Show cached test status without re-running. Use when checking test health, standup status, coverage summary, history, or identifying flaky tests from recent runs. license: MIT --- ## When to Use This Skill | Use this skill when... | Use test-run instead when... | |---|---| | Reading cached results without re-running tests | Actually executing the test suite | | Showing standup-ready test status from the last run | Triaging structured test output (use test-analyze) | | Spotting flaky tests via `--flaky` from recent runs | Picking which tier to run next (use test-tier-selection) | | Pulling a coverage summary from existing reports | Asking strategic questions (use test-consult) | ## Context Quick status check without re-running tests. Reads cached results from last test execution. **Use when:** - Checking current test health - Quick status update for standup - Reviewing before deciding next action ## Parameters - `--history`: Show trend from recent runs - `--coverage`: Include coverage summary - `--flaky`: Identify potentially flaky tests ## Cached Result Locations | Framework | Cache Location | |-----------|----------------| | pytest | `.pytest_cache/`, `htmlcov/` | | Vitest | `node_modules/.vitest/` | | Jest | `coverage/`, `.jest-cache/` | | Playwright | `test-results/`, `playwright-report/` | | Go | `coverage.out` | | Cargo | `target/debug/` | ## Behavior 1. **Find Latest Results**: - Check cache directories - Parse last run timestamp - Extract pass/fail counts 2. **Coverage Summary** (if --coverage): - Read coverage reports - Show percentage vs target - List uncovered files 3. **Flaky Detection** (if --flaky): - Compare recent runs - Identify tests with inconsistent results - Flag suspected flaky tests 4. **History** (if --history): - Show last 5 runs - Track pass rate trend - Identify regression patterns ## Output Format ``` ## Test Status (last run: 5 minutes ago) | Tier | Passed | Failed | Skipped | |-------------|--------|--------|---------| | Unit | 45 | 2 | 0 | | Integration | 12 | 0 | 1 | | E2E | 8 | 1 | 0 | **Coverage**: 78% (target: 80%) ### Recent Failures - test_user_validation: AssertionError (tests/test_user.py:42) - e2e/login.spec.ts: Timeout (line 15) ### Flaky Tests (if --flaky) - test_async_handler: 3 failures in last 10 runs ### Suggested Actions - Run `/test:quick` to verify current state - Use `/test:consult coverage` for gap analysis ``` ## Post-Actions - If failures exist: Suggest `/test:quick` to verify current state - If coverage low: Suggest `/test:consult coverage` - If flaky detected: Suggest `/test:consult flaky` - If stale (> 1 hour): Suggest running `/test:quick` or `/test:full`
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

