run-smoke-tests
Skill7 starsChanged 3 months agoMITView on GitHub
Run Playwright smoke tests, debug failures, and verify fixes. Use for smoke, e2e, Playwright, or pre-ship browser verification.
- Reads credentials
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- ArchitektApx/cursor-skills-for-claudeedited, first seen Nov 1, 2026
- dhanji4U/skillsedited, first seen Oct 2, 2026
- ElyzeSolutions/skillsedited, first seen Aug 6, 2026
- cogine-ai/cogine-dev-skillsetedited, first seen Jun 25, 2026
- microsoft/vscode-python-environmentstheir own version, first seen Feb 16, 2026
Used with
Projects with it also use check-compiler-errors, new-branch-and-pr and 3 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.
cogine-aiSkillcheck-compiler-errors
Run compile and type-check commands and report failures
Also in 3 projects that use this
- cogine-aiSkill
new-branch-and-pr
Create a fresh branch, complete work, and open a pull request
Also in 3 projects that use this
jaydubya818Skillmake-pr-easy-to-review
Use when a correct pull request needs clearer history, description, or reviewer guidance.
Also in 3 projects that use this
- jaydubya818Skill
get-pr-comments
Use when pull-request feedback needs to be fetched and summarized for action.
Also in 3 projects that use this
- +1 more from jaydubya818
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- cogine-ai/cogine-dev-skillset★ 452% same
- dhanji4U/skills★ 243% same
- ElyzeSolutions/skills★ 152% same
- ArchitektApx/cursor-skills-for-claude★ 052% same
Wrote their own version · 1
- microsoft/vscode-python-environments★ 147same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- browser-useSkill
- code-reviewSkill
- implementSkill
- leadSkill
- loop-on-ciSkill
- mermaidSkill
- tddSkill
- to-ticketsSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
6 rules. 3 are common, 1 is distinctive, and 2 are very specific to this project.
3
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 15
Run the relevant smoke suite or a focused test file.
- Common: line 16
If failing, inspect traces/logs and isolate the root cause.
- Distinctive: line 18
If the suite is green, say so and stop.
- Very specific: line 28
If the repo uses a different script (npm test, npx playwright test, make smoke), use that.
- Common: line 32
Prefer deterministic waits and assertions over brittle timeouts.
- Very specific: line 35
Never --no-verify. Never read .env or .env.local.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Run smoke tests
Trigger
Need end-to-end smoke verification before or after changes.
Workflow
- Build prerequisites for the target app.
- Run the relevant smoke suite or a focused test file.
- If failing, inspect traces/logs and isolate the root cause.
- Report the failure with evidence. Do not patch product code. Tech lead classifies. Bug implements.
- If the suite is green, say so and stop.
Example Commands
npm run smoketest
npm run smoketest -- path/to/test.spec.ts
npm run smoketest-no-compile -- path/to/test.spec.tsIf the repo uses a different script (npm test, npx playwright test, make smoke), use that. Do not invent a suite that is not in the checkout.
Guardrails
- Prefer deterministic waits and assertions over brittle timeouts.
- Re-run a green result once when flake is suspected. Report flake evidence.
- Quarantine tests only when explicitly requested and documented.
- Never
--no-verify. Never read.envor.env.local.
Output
- Test results summary
- Root cause for each failure, with a repro
- Remaining flake risk (if any)
Factory override
Report only. Do not implement the fix. Do not merge. Only the dispatched ticket or PR.
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.