E2E Evidence Per PR

Capture Playwright E2E screenshots and post them to pull requests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/davidlramirez95/towcommand --skill e2e-evidence-per-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: E2E Evidence Per PR
Source: https://github.com/davidlramirez95/towcommand/tree/main/.claude/skills/methodology/e2e-evidence-per-pr
Command: npx skills add https://github.com/davidlramirez95/towcommand --skill e2e-evidence-per-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that every Pull Request includes visual proof of changes through automated End-to-End (E2E) test screenshots, preventing visual regressions and creating a visual changelog.

Core Features & Use Cases

  • Mandatory Screenshot Evidence: Enforces Playwright screenshots for all E2E tests on every PR.
  • Visual Changelog: Builds a historical record of UI changes across PRs for easy comparison.
  • Regression Prevention: Catches unintended visual bugs that traditional assertions might miss.
  • Use Case: When a developer submits a PR for a new feature, this Skill automatically runs E2E tests, captures screenshots of key UI elements, uploads them to a dedicated branch, and posts a comment on the PR with embedded images, ensuring reviewers can visually verify the changes.

Quick Start

Run the E2E test suite and capture evidence by executing the command cd apps/mobile && pnpm test:e2e.

Frequently Asked Questions about E2E Evidence Per PR

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Playwright E2E test screenshots for every pull request?

To automate Playwright E2E test screenshots for every pull request, you can run the test suite to capture full-page screenshots, upload them to an orphan branch, and post a structured comment with embedded images to the PR.

What is the best way to create a visual changelog for UI changes across PRs?

Creating a visual changelog for UI changes is best achieved by enforcing mandatory screenshot evidence on every pull request, which captures and stores full-page screenshots to build a historical record of your application's visual changes.

How do visual regression screenshots prevent undetected UI bugs during code review?

Visual regression screenshots prevent undetected UI bugs by posting embedded images directly to the pull request, allowing reviewers to visually verify changes and catch unintended visual defects that traditional code assertions might miss.

Can I enforce mandatory E2E testing evidence on a pull request before merging?

Yes, you can enforce mandatory E2E testing evidence by configuring the workflow to capture full-page Playwright screenshots and post them as structured comments with embedded images directly to the pull request.

Does capturing full-page screenshots with Playwright require external dependencies?

Capturing full-page screenshots with Playwright does not require external dependencies, as the process utilizes internal scripts to run tests, upload images to an orphan branch, and generate pull request comments.

Why post E2E test screenshots to an orphan branch instead of standard repository storage?

Posting E2E test screenshots to an orphan branch isolates visual evidence from the main codebase, preventing repository bloat while still providing accessible embedded image links for structured pull request comments.