testing-validation
Skill2 starsChanged 31 days agoMITView on GitHub
Runs applicable validation layers and records evidence for Definition of Done
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mysleekdesigns/crawlforge-mcptheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mysleekdesigns/crawlforge-mcp★ 6same 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 repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- dependency-supply-chainSkill
- docker-cloudSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- package-registry-tiSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- procedure-playbooksSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- technology-intelligence-liveSkill
- worktree-orchestrationSkill
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 22
Run static analysis / lint when available.
- Distinctive: line 23
Run unit and integration tests for affected areas.
- Distinctive: line 24
Run end-to-end or browser checks for UI changes.
- Distinctive: line 30
If tests fail, fix implementation or report a blocker—never weaken tests to pass.
- Distinctive: line 31
Stop and report if budget limits are exceeded.
- Distinctive: line 39
Do not delete or weaken failing tests to force a green result.
- Distinctive: line 40
Do not claim validation passed without evidence.
- Distinctive: line 41
Do not skip applicable security or accessibility checks for UI/API changes.
≈ “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 Validation
Use this Skill when
Validating an implemented change, preparing a PR, or verifying Definition of Done.
Inputs
- Approved plan acceptance criteria
- Changed files
- Project test commands from TESTING.md / package scripts
- Autonomy budget limits
Procedure
- Identify applicable validation layers for the change.
- Run static analysis / lint when available.
- Run unit and integration tests for affected areas.
- Run end-to-end or browser checks for UI changes.
- Capture screenshots and logs under .agent/evidence/.
- Confirm build succeeds when applicable.
- Review rollback instructions against the change.
- For release closeout, run
./scripts/run-sandbox-release-smokes.shand gate with./scripts/validate-sandbox-release-smokes.sh --version X.Y.Z(M18). - If tests fail, fix implementation or report a blocker—never weaken tests to pass.
- Stop and report if budget limits are exceeded.
Output
Validation report with commands run, results, evidence paths, and remaining gaps.
Prohibited actions
- Do not delete or weaken failing tests to force a green result.
- Do not claim validation passed without evidence.
- Do not skip applicable security or accessibility checks for UI/API changes.
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.