test-and-verify
Skill1 starsChanged 46 days agoMITView on GitHub
Comprehensive test execution, typecheck, and build verification workflow for PaperDeck.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- melconcoast/code-ideatheir own version, first seen Nov 2, 2026
- sainzs/santiagosainz-skillstheir own version, first seen Oct 13, 2026
- cellrishi-code/claude-skills-atlastheir own version, first seen Oct 4, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- cellrishi-code/claude-skills-atlas★ 5same name
- melconcoast/code-idea★ 4same name
- sainzs/santiagosainz-skills★ 1same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-localeSkill
- create-widgetSkill
- diagnose-kindleSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
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 8
Use this skill to execute and diagnose automated tests, static typing, and production build pipelines.
- Distinctive: line 16
If a test fails, inspect the mock environment or missing collector exports.
- Distinctive: line 25
All types must resolve cleanly with 0 errors.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test and Verify Skill
Use this skill to execute and diagnose automated tests, static typing, and production build pipelines.
1. Run Unit Tests
npm test- Tests live in
test/and run using Node's built-innode:testrunner. - Expected output:
pass 40,fail 0. - If a test fails, inspect the mock environment or missing collector exports.
2. Run TypeScript Static Analysis
npm run typecheck- Executes both:
npm run typecheck:node(main process & preload viatsconfig.node.json)npm run typecheck:web(React renderer viatsconfig.web.json)
- All types must resolve cleanly with 0 errors.
3. Production Build Validation
npm run build- Executes
electron-vite build. - Generates bundles in
dist/main/,dist/preload/, anddist/renderer/.
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.

