e2e
Skill44 starsChanged 6 months agoMITView on GitHub
Guide for Playwright end-to-end tests. Use to create a new e2e test, debug a flaky test, or test API endpoints. Covers patterns, workarounds, and project conventions.
- Reads credentials
50 other projects use a version of this.
Adopted by
Most recently taken up by
- kortix-ai/sunatheir own version, first seen Nov 15, 2026
- varelaia/claude-skills-publictheir own version, first seen Nov 8, 2026
- sgaabdu4/appwrite-backendtheir own version, first seen Nov 8, 2026
- n1kben/agentstheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- jocarrd/crux-agentstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use instinct-export, instinct-import and 8 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.
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 4 projects that use this
0mlkrizzz655335vSkillsdk
Codex SDK 集成开发。用 TypeScript/Python SDK 做 agent 生命周期、流式输出、本地/云端执行等集成。
Also in 3 projects that use this
MontimageSkilltest-coverage
Improve test coverage by finding untested branches, error paths, and edge cases. Use when measuring or strengthening a project's tests. Don't use for production debugging, code review, or feature implementation.
Also in 3 projects that use this
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
- +1 more from TheKREATORS
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- kortix-ai/CompanyOS★ 21ksame name
- kortix-ai/suna★ 21ksame name
- tester-army/e2e★ 14ksame name
- elie222/inbox-zero★ 13ksame name
- getsentry/sentry-javascript★ 8.8ksame name
- entireio/cli★ 5.3ksame name
- callstack/react-native-pager-view★ 3.4ksame name
- openmeterio/openmeter★ 2.4ksame name
- stackia/rtp2httpd★ 2.3ksame name
- alibaba/loongcollector★ 2.2ksame name
40 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.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- create-docSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- event-stormingSkill
- implement-featureSkill
- product-managerSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- shipSkill
- skill-creatorSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read .claude/roles/code-reviewer.md — adopt this profile and follow all its rules.
“Common” is measured: kept by at least 6 in 10 of the 44 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
Playwright E2E Testing Guide
Persona
Read .claude/roles/code-reviewer.md — adopt this profile and follow all its rules.
Activation
This skill activates for:
- Creating a new e2e test
- Debugging a flaky test
- Testing a critical feature (complete API workflow)
Architecture
src/tests/e2e/
├── fixtures/
│ └── test-data.ts # Test data (webhooks, payloads, etc.)
├── specs/
│ ├── setup.ts # Server setup (run once)
│ └── <context>/
│ └── <feature>.spec.ts # Tests per feature
└── utils/
└── test-helpers.ts # Helpers (API calls, server setup)Commands
| Command | Usage |
yarn e2e | Run all tests |
yarn e2e:debug | Debug mode with inspector |
yarn test:e2e:report | View HTML report |
Workflow: Create a New Test
1. Identify the Context
specs/
├── setup.ts # Setup (do not touch)
├── webhook/ # Webhook endpoint tests
├── review/ # Review workflow tests
└── health/ # Health check tests2. Write the Test
// specs/webhook/github-webhook.spec.ts
import { test, expect } from "@playwright/test";
test.describe("GitHub Webhook", () => {
test("should accept a valid pull request event", async ({ request }) => {
const response = await request.post("/webhooks/github", {
headers: {
"content-type": "application/json",
"x-github-event": "pull_request",
"x-hub-signature-256": "sha256=valid-signature",
},
data: {
action: "opened",
pull_request: {
number: 42,
title: "feat: add new feature",
head: { ref: "feat/new-feature" },
base: { ref: "main" },
},
repository: { full_name: "org/repo" },
sender: { login: "developer" },
},
});
expect(response.status()).toBe(200);
});
test("should reject an invalid payload", async ({ request }) => {
const response = await request.post("/webhooks/github", {
data: {},
});
expect(response.status()).toBe(400);
});
});3. Run and Validate
# Debug mode
yarn e2e:debug
# Run a single file
yarn e2e specs/webhook/github-webhook.spec.tsSelectors (priority for UI tests)
| Priority | Type | Example |
| 1 | data-testid | [data-testid="submit-btn"] |
| 2 | Role (accessibility) | getByRole("button", { name: "Submit" }) |
| 3 | Text | getByText("Submit") |
| 4 | CSS (last resort) | table tbody tr |
Authentication for API Tests
Token-based Authentication
test.describe("Authenticated API", () => {
test("should return review status with valid token", async ({ request }) => {
const response = await request.get("/api/reviews/123", {
headers: {
Authorization: `Bearer ${process.env.TEST_API_TOKEN}`,
},
});
expect(response.status()).toBe(200);
const body = await response.json();
expect(body).toHaveProperty("status");
});
});Fixtures and Test Data
Use existing fixtures
import { TEST_WEBHOOKS, TEST_PAYLOADS } from "../fixtures/test-data";
test("should process a GitLab merge request event", async ({ request }) => {
const response = await request.post("/webhooks/gitlab", {
data: TEST_PAYLOADS.gitlabMergeRequest,
});
expect(response.status()).toBe(200);
});Add test data
// fixtures/test-data.ts
export const TEST_PAYLOADS = {
gitlabMergeRequest: {
object_kind: "merge_request",
object_attributes: {
iid: 1,
title: "feat: add review automation",
action: "open",
},
},
githubPullRequest: {
action: "opened",
pull_request: {
number: 42,
title: "fix: resolve webhook validation",
},
},
};Debugging Flaky Tests
1. Debug mode
yarn e2e:debug specs/webhook/my-test.spec.ts2. Trace on failure
Traces are enabled on the first retry. After a failure:
yarn test:e2e:report3. Logs
// Add checkpoints
console.log("Step: Sending webhook payload");4. Stabilization Patterns
// Flaky: not waiting for server readiness
await request.post("/webhooks/github", { data: payload });
// Stable: verify server is ready first
const health = await request.get("/health");
expect(health.status()).toBe(200);
await request.post("/webhooks/github", { data: payload });New Test Checklist
- Test data uses fixtures (not hardcoded)
- Assertions use
expect()from Playwright - Test runs in isolation (no dependency on other tests)
- API responses are properly validated (status + body)
- Error cases are covered (invalid payloads, missing auth)
Anti-patterns
| Avoid | Prefer |
| Hardcoded test data | Fixtures from test-data.ts |
| Tests dependent on each other | Isolated tests |
| Missing error case coverage | Test both success and failure paths |
| Ignoring response body | Validate status AND body structure |
Arbitrary waitForTimeout | Proper readiness checks |
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.

