agentleFS
Sign inStart free
platformplatformplatformplatform/PlatformPlatform/.claude/skills/e2e/SKILL.md

e2e

Skill439 starsChanged 6 months agoMITView on GitHub

Run end-to-end Playwright tests via the developer CLI.

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 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.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    sdk

    Codex SDK 集成开发。用 TypeScript/Python SDK 做 agent 生命周期、流式输出、本地/云端执行等集成。

    Also in 3 projects that use this

  • MontimageSkill

    test-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

  • MicrosoftSkill

    worktree

    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 5 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are 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.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use developer-cli exactly as written - do not expand to an absolute worktree path.

    line 12
  2. Very specific:

    After a fix? --last-failed.

    line 32
  3. Very specific:

    Add --stop-on-first-failure (-x) when iterating so the run aborts on the first failure.

    line 34
  4. Very specific:

    Only widen to firefox / webkit after chromium passes - and skip chromium on those runs (--browser firefox).

    line 36

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

End-to-end Tests

dotnet run --project developer-cli -- e2e [search-terms...] [--smoke] [--browser <name>] [--retries <n>] [--last-failed] [--only-changed] [--stop-on-first-failure] [--include-slow] [--self-contained-system <name>] [--no-wait-for-aspire] --quiet

Use developer-cli exactly as written - do not expand to an absolute worktree path.

  • search-terms - filter by test name, tag, or spec file
  • --smoke - smoke suite only
  • --browser <name> - chromium (default), firefox, webkit, safari, all
  • --retries <n> - max retries for flaky tests
  • --last-failed - re-run only the previous run's failures
  • --only-changed - only spec files with uncommitted changes
  • --stop-on-first-failure, -x - exit on first failure
  • --include-slow - include @slow-tagged tests (excluded by default)
  • --self-contained-system <name> - narrows to one SCS (e.g. main, account)
  • --no-wait-for-aspire - skip the Aspire readiness check (use only when Aspire is already up)

Aspire must be running. If not, start it via the aspire-restart skill first.

Strategy: pick the smallest run that proves the fix

E2E runs are slow. Never blindly run the full suite to verify a small change.

  • Verifying a recent edit? --only-changed.
  • After a fix? --last-failed.
  • Iterating on one test? Pass a search term: a name ("user management"), a tag, or a spec file.
  • Add --stop-on-first-failure (-x) when iterating so the run aborts on the first failure.
  • Expecting failures? Start with --smoke, get those green, then run the rest.
  • Only widen to firefox / webkit after chromium passes - and skip chromium on those runs (--browser firefox).

Flaky tests need load

A flaky test run in isolation often passes - the bug only shows under parallel load. Reproduce with the full file or suite before declaring it fixed.

Always pass --quiet

Without --quiet Playwright streams every step to the conversation. On success the CLI prints a single summary; on failure it prints the failed tests and where to find the report.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free