e2e-for-featurelisted

Automatically create E2E test scenarios that prove a new feature works. Use this skill when a PR or branch introduces a new feature and you want to generate an end-to-end scenario that exercises it, takes screenshots at key points, and verifies the screenshots show the expected behavior. Trigger when: the user says "create e2e for this feature", "write an e2e test for this PR", "prove this feature works with e2e", "add e2e coverage for this change", or any variation of wanting automated E2E proof that new code works. Also use when the user asks to "test this feature end to end" or "create a scenario for the new feature". Do NOT use for fixing existing failing scenarios (use e2e-testing), manual debugging (use e2e-manual-debugging), or reviewing baselines (use baseline-review).
gpambrozio/Gallager · ★ 3 · Testing & QA · score 69

Install: claude install-skill gpambrozio/Gallager

# E2E Scenario Creation for New Features This skill automates the full workflow of creating an E2E test scenario that proves a new feature works: analyze the PR, write the scenario, run it until it passes, and verify screenshots show the expected content. ## Prerequisites Before starting, load the E2E testing reference material. Read these files from the existing e2e-testing skill: - `.claude/skills/e2e-testing/references/test-steps-reference.md` — all TestStep signatures (including the `instance:` parameter on every macOS step, hook events, scripts, file/clipboard helpers, version-compatibility steps) - `.claude/skills/e2e-testing/references/patterns.md` — common scenario patterns (multi-instance, hook events, script injection, terminal content assertions, version mismatch, …) - `.claude/skills/e2e-testing/references/element-queries.md` — ElementQuery matching, including `.help` and `.anyTextMatches` Also read `docs/e2e-testing.md` in the project root for screenshot comparison and failure-screenshot details. ## Workflow ### Phase 1: Understand what the PR implements Run `git diff main...HEAD --stat` and `git log main..HEAD --oneline` to see what changed. Then read the key changed files to understand: - **What new UI elements were added?** (buttons, views, screens, settings) - **What user-facing behavior changed?** (new flows, new states, new interactions) - **Which platforms/instances are affected?** (iOS, macOS host, macOS viewer, two-Mac, server) - **Are there new