Generate end-to-end test artifacts from a GitHub issue number and attach them to pull requests.
npx skills add https://github.com/ranvirsingh/speckit --skill speckit-e2e
Please help me install this Agent Skill. Skill: speckit-e2e Source: https://github.com/ranvirsingh/speckit/tree/main/skills/speckit-e2e Command: npx skills add https://github.com/ranvirsingh/speckit --skill speckit-e2e
Generate end-to-end test artifacts that prove implementations work and become part of the CI pipeline, attaching results to PR descriptions to streamline QA and verification.
Provide a GitHub issue number and acceptance scenarios to generate end-to-end artifacts and attach them to the corresponding PR.
High-intent search queries and answers about installing and using this skill.
Automate end-to-end test artifacts by providing a GitHub issue number and acceptance scenarios to generate proof-of-work results and update the corresponding PR description automatically.
Yes, Playwright tests with video recording can be generated for UI projects to exercise acceptance scenarios, producing visual proof that the implementation works for PR verification.
Generate equivalent proof-of-work artifacts for non-UI projects like APIs, CLIs, or libraries by providing a GitHub issue number to produce verification outputs without UI tests.
End-to-end test artifact generation should be run after UAT and before the retrospective phase, integrating into the CI/CD pipeline to attach verification proof to PR descriptions.
Yes, a GitHub issue number is required as input to integrate with the speckit workflow, emit the end-to-end test artifacts, and update the related PR description with results.
simplerick0Analyze a GitHub issue, implement a fix, and create a pull request.
rbah31Automate end-to-end sprint cycles with phase-isolated claude -p sessions.
matteocervelliGenerate Playwright end-to-end tests using the page object model.
minicooheiGenerate structured test plans, test cases, and Playwright E2E templates from use-case descriptions.
