pr-proof-of-workTDD-driven E2E workflow with real Playwright browser screenshots as PR proof. Use when: (1) fix bugs or implement features with test-first approach, (2) crea...
Install via ClawdBot CLI:
clawdbot install newtontech/pr-proof-of-workGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/${REPO}/raw/${BRANCH}/e2e-screenshots/${TEST_DIR}/${BEFORE_FIAudited Apr 18, 2026 · audit v1.0
Generated May 6, 2026
A developer identifies an open issue in a web application, writes a Playwright E2E test that captures a 'before' screenshot showing the bug, implements the fix, and captures an 'after' screenshot. The PR includes a side-by-side comparison, providing undeniable visual evidence of the fix.
When adding a new feature, the developer first writes an E2E test that defines the expected behavior, then implements the feature until the test passes. Screenshots document the initial state and the final working feature, ensuring the implementation meets requirements.
A team sets up automated E2E tests that run on every PR, capturing screenshots at key states. Any visual regression is immediately visible in the PR comments, allowing reviewers to catch unintended changes quickly.
For a backend change that affects UI indirectly (e.g., a new API endpoint, configuration change), the developer writes an E2E test that exercises the related UI path (e.g., opening settings, running a terminal command) and captures screenshots to demonstrate the change works correctly end-to-end.
Open-source projects use this workflow to guide new contributors: pick an issue, write a test, fix, and submit a PR with screenshots. The structured process ensures contributions are testable and visually verifiable.
Offer a basic version of the TDD-E2E-PR workflow as a CLI tool or GitHub Action for free, with premium features like advanced analytics, team dashboards, and priority support via a subscription.
Provide consulting to integrate this workflow into client development pipelines, along with training workshops on TDD, Playwright, and CI/CD best practices.
Build a cloud platform that hosts E2E test runs, stores screenshots, and provides a visual diff review interface. Integrate with GitHub to automatically post screenshot comparisons.
💬 Integration Tip
Integrate with GitHub Actions by using the workflow commands provided in the SKILL.md; store screenshots as artifacts and reference them via raw GitHub URLs for PR comments.
Scored May 6, 2026
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection
Browser automation via Playwright MCP server. Navigate websites, click elements, fill forms, extract data, take screenshots, and perform full browser automation workflows.
Browser automation via Playwright MCP. Navigate websites, click elements, fill forms, take screenshots, extract data, and debug real browser workflows. Use w...
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with w...