e2e-test-writer
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Use this skill whenever the user asks to write, generate, review, or improve end-to-end (E2E) tests — tests that drive a real user journey through the fully deployed/running application, typically via a real browser or client, regardless of language or tooling (Playwright, Cypress, Selenium, WebDriver, Appium, etc.). Trigger this for requests like "write E2E tests for the checkout flow", "test this user journey in the browser", "add Playwright/Cypress tests", "automate this UI flow", or "test the app end to end", even if no specific tool is named. This is distinct from unit-test-writer (isolated single-unit logic, dependencies mocked) and integration-test-writer (internal component/service seams like API+DB) — use this skill instead when the request is about simulating what a real user does through the actual UI/client against a fully running system.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Sagargupta16/agent-recipestheir own version, first seen Nov 1, 2026
- dayvisonassis/sdd-skillstheir own version, first seen Oct 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Sagargupta16/agent-recipes★ 4same name
- dayvisonassis/sdd-skills★ 3same 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 repository6 other files it gives its agents.
- daily-taskSkill
- integration-test-writerSkill
- presentational-component-writerSkill
- prompt-optimizerSkill
- pushSkill
- unit-test-writerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.