e2e
Skill1 starsChanged 8 months agoNo licenceView on GitHub
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
- Reads credentials
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
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 measured: kept by at least 6 in 10 of the 38 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.
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- PatriotAgenticLLC/better_claude_skillz★ 378% same
Wrote their own version · 43
- kortix-ai/suna★ 20ksame name
- elie222/inbox-zero★ 13ksame name
- tester-army/e2e★ 12ksame name
- getsentry/sentry-javascript★ 8.8ksame name
- entireio/cli★ 5.2ksame name
- callstack/react-native-pager-view★ 3.4ksame name
- openmeterio/openmeter★ 2.4ksame name
- stackia/rtp2httpd★ 2.3ksame name
- alibaba/loongcollector★ 2.2ksame name
- lodev09/react-native-true-sheet★ 2.1ksame name
33 more not listed
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.
Used alongsideProjects with it also use logging, worktree and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
diego-tobalinaSkilllogging
Logging best practices for Java (SLF4J/Logback) and Node.js (Winston/Pino). Use for structured logging, log levels, and avoiding sensitive data exposure.
Also in 3 projects that use this
MicrosoftSkillworktree
Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.
Also in 4 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 7 projects that use this
MicrosoftSkillspec-review
Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.
Also in 3 projects that use this
In this repository59 other files it gives its agents.
- asideSkill
- brainstormSkill
- build-fixSkill
- checkpointSkill
- clawSkill
- code-reviewSkill
- cpp-buildSkill
- cpp-reviewSkill
- cpp-testSkill
- devfleetSkill
- docsSkill
- evalSkill
- evolveSkill
- execute-planSkill
- go-buildSkill
- go-reviewSkill
- go-testSkill
- gradle-buildSkill
- harness-auditSkill
- instinct-exportSkill
- instinct-importSkill
- instinct-statusSkill
- kotlin-buildSkill
- kotlin-reviewSkill
- kotlin-testSkill
- learn-evalSkill
- learnSkill
- loop-startSkill
- loop-statusSkill
- model-routeSkill
- multi-backendSkill
- multi-executeSkill
- multi-frontendSkill
- multi-planSkill
- multi-workflowSkill
- orchestrateSkill
- planSkill
- pm2Skill
- projectsSkill
- promoteSkill
- prompt-optimizeSkill
- python-reviewSkill
- quality-gateSkill
- refactor-cleanSkill
- resume-sessionSkill
- rust-buildSkill
- rust-reviewSkill
- rust-testSkill
- save-sessionSkill
- sessionsSkill
- setup-pmSkill
- skill-createSkill
- skill-healthSkill
- tddSkill
- test-coverageSkill
- update-codemapsSkill
- update-docsSkill
- verifySkill
- write-planSkill
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.

