testing-and-quality
Skill0 starsChanged 3 days agoMITView on GitHub
Choose focused automated tests and quality checks that verify user-visible behavior and protect important invariants.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- dynamics365ninja/d365fo-clitheir own version, first seen Oct 29, 2026
- nikzlabs/shipittheir own version, first seen Oct 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dynamics365ninja/d365fo-cli★ 45same name
- nikzlabs/shipit★ 9same 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 repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- image-art-directionSkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- responsive-designSkill
- saas-dashboardSkill
- security-engineeringSkill
- super-admin-panelSkill
- unslop-engineSkill
- ux-researchSkill
- visual-designSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 10
Use for feature implementation, bug fixes, refactors, and test strategy.
- Distinctive: line 14
Do not add brittle tests solely to increase coverage or duplicate tests that assert the same behavior at every layer.
- Distinctive: line 28
Use fixtures that are realistic but deterministic.
- Distinctive: line 30
Avoid asserting private implementation details unless they are part of a supported contract.
- Distinctive: line 32
Run targeted tests, then broader checks when shared behavior changes.
- Distinctive: line 39
Prefer regression tests that fail before the fix.
- Distinctive: line 40
Keep security and authorization boundaries directly tested.
- Distinctive: line 41
Do not weaken assertions to make a failing suite green.
≈ “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
Testing and Quality
When to use
Use for feature implementation, bug fixes, refactors, and test strategy.
When not to use
Do not add brittle tests solely to increase coverage or duplicate tests that assert the same behavior at every layer.
Inputs and assumptions
Inspect the test runner, project conventions, critical user flows, existing regressions, dependency boundaries, and CI constraints.
Workflow
- State the behavior or invariant that could fail.
- Choose the narrowest test layer that gives reliable evidence; add integration or browser tests for real boundary behavior.
- Cover success, important boundary cases, and meaningful failures.
- Use fixtures that are realistic but deterministic; isolate filesystem, network, time, and external services where needed.
- Avoid asserting private implementation details unless they are part of a supported contract.
- Run targeted tests, then broader checks when shared behavior changes.
- Report exact commands and limitations; do not claim unrun checks passed.
Decision rules
- A passing test is evidence for its assertion, not proof of total correctness.
- Prefer regression tests that fail before the fix.
- Keep security and authorization boundaries directly tested.
- Do not weaken assertions to make a failing suite green.
Example
For a retry fix, assert both that transient failures retry within the configured bound and that a permanent validation error is not retried.
Common failures
- Snapshot updates that conceal behavioral regressions.
- Tests that depend on order, wall-clock timing, or external network state.
- Testing only helper functions while skipping the integration boundary.
Validation
Confirm the test fails for the relevant regression, passes after the change, is deterministic, and the reported command actually ran.
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.