Plan and execute frontend QA workflows from branch diffs with HTML reports.
npx skills add https://github.com/gewoonseba/dotfiles --skill qa-gewoonseba
Please help me install this Agent Skill. Skill: qa Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/frontend-qa Command: npx skills add https://github.com/gewoonseba/dotfiles --skill qa-gewoonseba
Frontend QA reduces the risk of regressions by orchestrating a two-phase approach: plan testing from the current branch diff and validate the plan in a browser, producing an actionable HTML report with screenshots.
Follow the two-phase workflow: generate a testing plan from the diff, review and approve it, then execute tests in a local browser and produce an HTML report.
High-intent search queries and answers about installing and using this skill.
Frontend QA from a git diff involves analyzing branch changes to generate a test plan, then validating UI behavior in a local browser to produce an HTML report with screenshots. This approach uses a two-phase workflow to verify components and routing before merging.
A two-phase QA workflow first plans tests by analyzing the git diff of a feature branch, then executes those tests in a local browser. It produces an HTML report with screenshots documenting pass or fail results for UI changes, accessibility, and visual correctness.
To generate an HTML report with screenshots for UI regression testing, you execute a browser validation phase against a planned test suite. This Skill outputs a comprehensive HTML report documenting pass or fail results with local browser screenshots after verifying the diff.
Yes, you can verify frontend routing and component changes before merging by running a QA workflow that analyzes the branch diff. It converts code changes into targeted test plans and validates them in a local browser to ensure UI behavior and accessibility standards are met.
No external testing dependencies are required to run this QA workflow. The Skill operates independently with no listed dependencies, using its own agent orchestration to plan from the git diff and validate changes directly in a local browser environment.
Automated browser validation for frontend changes should be used when reviewing a feature branch before merging to reduce regression risks. It is ideal for confirming that UI behavior, accessibility, and visual correctness remain intact after component or routing updates.
BrightBlockCreate a git worktree and initialize dependencies for branch review.
mattbutlerengineeringClassify Playwright visual diff failures as intentional, regression, or stale.
levinbaenningerVerify Next.js runtime behavior by synchronizing framework diagnostics with browser-based interaction testing.
DarkMonkDevRun unit, integration, and end-to-end tests in isolated containers.
