e2e-verify
Skill4 starsChanged 20 days agoMITView on GitHub
Plan and execute end-to-end verification with explicit scope, test data, environments, and acceptance criteria.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- miinhho/skillstheir own version, first seen Nov 1, 2026
- Robbyfree24/ai-dev-pipeline-their own version, first seen Oct 20, 2026
- quocld/hephaestus-agent-skillstheir own version, first seen Oct 20, 2026
- bifrost-proxy/bifrosttheir own version, first seen Oct 9, 2026
- dennisrongo/claude-skillstheir own version, first seen Aug 16, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- bifrost-proxy/bifrost★ 168same name
- quocld/hephaestus-agent-skills★ 8same name
- miinhho/skills★ 2same name
- dennisrongo/claude-skills★ 1same name
- Robbyfree24/ai-dev-pipeline-★ 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 repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditorSkill
- api-contract-reviewSkill
- backend-releaseSkill
- bug-diagnosisSkill
- client-copy-reviewSkill
- codebase-designSkill
- code-reviewSkill
- create-issueSkill
- create-prSkill
- create-taskSkill
- dependency-upgradeSkill
- deploy-evidenceSkill
- design-expertSkill
- design-system-docsSkill
- design-system-setupSkill
- domain-modelingSkill
- evidence-auditSkill
- feature-discoverySkill
- frontend-releaseSkill
- generate-readmeSkill
- handoffSkill
- implement-taskSkill
- incident-responseSkill
- init-projectSkill
- live-docsSkill
- mcp-debuggingSkill
- memory-curatorSkill
- plan-expertSkill
- planning-featuresSkill
- project-memory-initSkill
- project-memory-refreshSkill
- project-profileSkill
- project-releaseSkill
- proof-runnerSkill
- release-checklistSkill
- researchSkill
- security-hardeningSkill
- security-reviewSkill
- tddSkill
- wiki-forgeSkill
- wiki-initSkill
- wiki-querySkill
- wiki-syncSkill
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 4 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 12
Use synthetic or explicitly approved accounts/data.
- Distinctive: line 13
Run the narrowest representative flow, then relevant regression coverage.
- Distinctive: line 23
All paths require explicit test scope and data.
“Common” is measured: kept by at least 6 in 10 of the 4 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
End-to-End Verify
Intent: e2e_test — EN: end-to-end test, browser flow, user journey verification. ES: prueba end-to-end, flujo de navegador, verificar recorrido de usuario.
- Define the user journey, entry URL, environment, supported browsers/hosts, preconditions, test data, cleanup, and pass/fail criteria before running tests.
- Inspect existing test tools and scripts first. Prefer existing Playwright/Cypress/framework conventions; do not add dependencies without approval.
- Use synthetic or explicitly approved accounts/data. Never expose credentials in logs, screenshots, traces, or reports. Avoid destructive production actions.
- Run the narrowest representative flow, then relevant regression coverage. Capture command, environment, result, and artifact locations.
- Distinguish a browser automation pass from backend/provider/live-tenant proof. Report blocked, skipped, flaky, and manually verified cases separately.
- Clean up created data when safe and authorized; state anything left behind.
Host paths and limits
- Claude Code: use the project's configured browser/test tooling; browser-control availability is environment-specific.
- Codex CLI: use available terminal/browser tools and repository scripts; a static check is not browser proof.
- OpenCode: use configured tools/plugins only; do not assume browser control is installed.
All paths require explicit test scope and data. No host receives implicit credentials or third-party configuration.
Resumen (ES)
Define recorrido, entorno, datos sintéticos/autorizados, criterios y limpieza antes de probar. Separa automatización local de evidencia en producción/proveedor, protege credenciales y reporta casos omitidos, inestables o bloqueados.
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.