Capture before/after screenshots, Playwright traces, videos, and browser error logs for UI code changes.
npx skills add https://github.com/mitchellfyi/dex --skill dxuicapture
Please help me install this Agent Skill. Skill: dxuicapture Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxuicapture Command: npx skills add https://github.com/mitchellfyi/dex --skill dxuicapture
Manually capturing consistent before/after visual evidence for UI changes is time-consuming and easy to forget, leading to incomplete PR reviews, missed regressions, and extra back-and-forth with reviewers.
Use the dxuicapture skill to capture before and after visual evidence for the new user onboarding flow you just implemented, including screenshots, a video walkthrough, and browser error logs.
High-intent search queries and answers about installing and using this skill.
To capture before and after screenshots for a pull request review, this Skill automates visual evidence collection including Playwright traces, videos, and browser error logs. It organizes these artifacts in a standardized manifest with absolute file links for easy reviewer access.
Visual regression testing evidence is the visual proof captured before and after browser-facing code changes to detect unintended UI modifications. You need it when updating frontend components, styles, or user flows to ensure no regressions are introduced during pull request reviews.
Yes, this UI capture approach works with React, Vue, and Next.js frameworks. It applies to any UI-affecting work including frontend component updates, style changes, new user flows, and browser behavior modifications across web frameworks.
To generate Playwright traces and videos for bug fixes, use this Skill to automatically capture browser interactions and console logs. It creates standardized artifacts organized in a manifest, ready to attach to your PR for comprehensive visual regression debugging.
The best way to automate screenshot capture for frontend code changes is using a Skill that grabs before and after visual evidence, records video walkthroughs, and collects browser error logs. This standardized approach prevents missed regressions and reduces reviewer back-and-forth.
You need browser error logs and console output for PR handoff to prove no regressions were introduced during UI changes. This Skill captures network logs alongside screenshots and videos, providing reviewers complete context to validate browser behavior modifications.
TavokAITest local web applications with Playwright, capturing screenshots and console logs.
CommunityToolkitCapture Playwright screenshots and embed them in GitHub PR descriptions.
matteocervelliGenerate Playwright end-to-end tests using the page object model.
alvarettoCompare generated images against originals and report visual differences.
