om-ux-review-pr

Reviews a PR's UI in a real browser and posts evidence-backed design findings.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-ux-review-pr-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-ux-review-pr
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-ux-review-pr
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-ux-review-pr-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Design review of pull requests is often skipped or reduced to subjective opinions. This Skill walks the changed screens in a real browser, performs the user's actual tasks, and produces findings where every recommendation carries evidence, a pattern, a trade-off, and an acceptance criterion. ## Core Features & Use Cases - Browser-based walkthrough: Starts the PR's app, enters each changed screen as its user, and performs primary tasks (create, edit, delete) rather than just viewing pages. - Structured findings: Ranks issues by impact, frequency, and reach, tagging each claim with an honest evidence tier from product contract down to labeled assumption. - State and humane checks: Verifies empty, loading, error, and narrow-viewport states, and screens for deceptive patterns like hidden costs, confirmshaming, and fake urgency. - Tracker integration: Posts one marker-idempotent review comment on the PR with attached screenshot evidence, or returns the report locally when no PR exists. - Use Case: Before merging a pull request that changes a checkout flow, run this Skill to walk the flow in a browser, capture screenshots of each state, and receive a ranked review comment citing WCAG or the repo's design contract for each finding. ## Quick Start Review the UI changes in pull request 42 by walking the affected screens in a browser and posting an evidence-backed design review comment.

Frequently Asked Questions about om-ux-review-pr

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

FAQPage Schema
How do I review the UI changes of a pull request automatically?

Provide a PR number and the skill starts the app, walks each changed screen in a browser performing real user tasks, and posts one review comment with findings ranked by user impact, each with evidence, a pattern, a trade-off, and an acceptance criterion.

Can I run a UX review before opening a pull request?

Yes. When given a branch with no open PR, or no argument at all, the skill diffs against the base branch, runs the same walk locally, and returns the report directly without posting anything to the tracker.

Does the UX review check accessibility and dark mode?

The state matrix covers default, empty, loading, error, no-permission, long-content, and narrow-viewport states. Theming is checked through the app's own theme toggle; if none is reachable, the dark-mode pass is reported as not performed rather than skipped silently.

What happens when a repository has no design contract?

Without a .uxproof contract, tier-one PRODUCT findings are unavailable and the report states this on its Contract line. The review then judges against standards, platform conventions, research, heuristics, and labeled assumptions only.

Will the review comment duplicate if the skill runs twice?

No. The review comment carries a text marker on its first line; a re-run finds the existing comment via list-issue-comments and updates it in place instead of posting a second one.

When should I use om-ux-shape instead of a PR review?

Use om-ux-shape in Review mode when the subject is a whole module, flow, or existing product area rather than the increment a single PR ships. This skill's scope guard redirects such requests and its walk procedure is reused there for evidence gathering.