regression-health-digest
Skill1 starsChanged 29 days agoMITView on GitHub
Summarize recent regression/CI test runs into a health digest covering pass rate, new failures, flaky suspects, slowest tests, and recommended actions.
In this repository16 other files it gives its agents.
- accessibility-auditSkill
- api-test-generatorSkill
- automation-code-reviewSkill
- bug-report-writerSkill
- ci-cd-and-test-dataSkill
- device-cloud-setupSkill
- flaky-test-triageSkill
- framework-scaffolderSkill
- greenbuild-getting-startedSkill
- llm-app-testingSkill
- mobile-automationSkill
- performance-test-starterSkill
- release-readiness-checklistSkill
- test-plan-from-requirementsSkill
- tools-and-librariesSkill
- visual-testingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Never mark something as passing without run data.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Regression suite health digest
- Pull the last N runs (default 7 days) from CI or reports (GitHub Actions, JUnit XML, Allure, Playwright JSON). If there is no access, ask the user to paste or upload them.
- Compute: total, pass, fail and skip counts; pass rate per run and the trend; duration trend.
- Classify failures:
- New failure: first failed in this window, and still failing (likely a regression)
- Flaky suspect: both passed and failed on the same commit or branch
- Known/quarantined: on a list saved in memory
- Top 5 slowest tests and the top 5 most frequent failures.
- Output a digest under 20 lines: headline status (Healthy/Watch/Unhealthy, with thresholds stated), key numbers, a table of issues with suggested owners, and 3 recommended actions.
- Never mark something as passing without run data. Clearly label any numbers that were estimated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.