test-check
Skill73 starsChanged 4 months agoMITView on GitHub
MUST use after implementing new features or bug fixes, when user asks 'run the tests', 'are tests passing?', 'test this', or before any deployment step. Also trigger when tests were previously failing and fixes were applied.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- exerias21/brainstorm-toolkittheir own version, first seen Oct 4, 2026
- braincandy-parallel/tamarindos-workflow-kittheir own version, first seen Sep 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- braincandy-parallel/tamarindos-workflow-kit★ 0same name
- exerias21/brainstorm-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- memory/CLAUDE.mdCLAUDE.md
- changelogSkill
- db-checkSkill
- deploy-checkSkill
- e2e-checkSkill
- elicit-requirementsSkill
- load-sessionSkill
- pr-reviewSkill
- register-projectSkill
- review-diffSkill
- review-fullSkill
- save-diarySkill
- save-sessionSkill
- scaffold-projectSkill
- self-auditSkill
- session-endSkill
- sprint-planSkill
- statusSkill
- tech-radarSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Run the full test suite and provide analysis:
- Very specific: line 10
Check CLAUDE.md or the project manifest (package.json, pyproject.toml, Gemfile, pom.xml, etc.) for the test command
- Distinctive: line 12
Default (no context): ask which project
- Distinctive: line 13
Run the appropriate test command and capture output
- Distinctive: line 15
If failures exist: analyze root cause of each failing test
- Distinctive: line 17
Check CLAUDE.md for the documented test baseline count for the active project
- Distinctive: line 18
If no baseline is documented: parse the test summary output line for total count.
- Distinctive: line 19
If actual count is higher than baseline, the test suite grew.
- Distinctive: line 20
Check if recently modified files have corresponding tests
- Distinctive: line 24
Check CLAUDE.md for the dev server port and E2E test command
- Distinctive: line 25
Check if dev server is running on that port before proceeding
- Very specific: line 26
Run E2E test command from CLAUDE.md (e.g., yarn test:e2e or npm run test:e2e, or the project's E2E command)
- Distinctive: line 30
If dev server is NOT running, report and skip (do NOT auto-start)
≈ “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
Run the full test suite and provide analysis:
- Detect active project from current working directory or recent context:
- Check
CLAUDE.mdor the project manifest (package.json, pyproject.toml, Gemfile, pom.xml, etc.) for the test command - Common patterns:
yarn test:unit/npm test/npx vitest run(JS),pytest(Python),bundle exec rspec(Ruby),go test ./...(Go),mvn test(Java),cargo test(Rust),dotnet test(.NET) - Default (no context): ask which project
- Check
- Run the appropriate test command and capture output
- Report summary: total tests, passed, failed, skipped, duration
- If failures exist: analyze root cause of each failing test
- Compare against known baselines:
- Check
CLAUDE.mdfor the documented test baseline count for the active project - If no baseline is documented: parse the test summary output line for total count; compare against previous runs if agent memory has a baseline
- If actual count is higher than baseline, the test suite grew; if lower, investigate missing tests
- Check
- Check if recently modified files have corresponding tests
- Identify test coverage gaps for critical paths
- Suggest new tests if coverage is insufficient
- E2E tests (run if user says "e2e", "all", or "full"):
- Check
CLAUDE.mdfor the dev server port and E2E test command - Check if dev server is running on that port before proceeding
- Run E2E test command from
CLAUDE.md(e.g.,yarn test:e2eornpm run test:e2e, or the project's E2E command) - E2E baselines: documented in
CLAUDE.md - Parse the E2E runner's output (Playwright, Cypress, Selenium, Capybara, etc.): passed/failed/skipped counts
- On failure: note which spec file and test name failed
- If dev server is NOT running, report and skip (do NOT auto-start)
- Check
Present results in a clear dashboard format.
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.