Code Review & Testing · IN-DEPTH PROFILE

web-design-reviewer

Browser-based visual review for responsive, accessible, consistent web interfaces with source-level fixes.

Best for

Frontend teams reviewing a site before release

What you get

Inspect the running site + Trace issues to source

Main limitation

Requires a running target, browser automation, and source access for fixes.

First risk

Unintended changes during remote review. Browser actions or source edits against a production target can alter data or broaden the change. Keep production review read-only, confirm the source workspace, and test fixes locally.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 318066d2

Open pinned commit
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Web Design Reviewer is a GitHub Awesome Copilot workflow for inspecting a running website across mobile, tablet, desktop, and wide viewports, locating design problems in the source, applying minimal fixes, and re-verifying the result.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.agents/skills/web-design-reviewer/
Personal scope~/.copilot/skills/web-design-reviewer/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add github/awesome-copilot --skill web-design-reviewer --agent github-copilot
Official agent docs

Copilot also accepts .github/skills and .claude/skills at project scope. Preview untrusted Skills before enabling scripts.

View path evidence

TYPICAL WORKFLOW

A practical workflow

01

Inspect the running site

Capture the page and review layout, responsiveness, accessibility, and consistency.

02

Trace issues to source

Find the owning component or style rule for each visible defect.

03

Fix and re-verify

Apply minimal source changes and repeat the viewport checks.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Connects visible problems to concrete source-level fixes.
  2. Covers responsive and accessibility failures alongside visual consistency.

Limitations

  1. Requires a running target, browser automation, and source access for fixes.
  2. A fixed viewport checklist cannot replace device testing, user research, or full accessibility auditing.

BEST FIT

Who it is for

Frontend teams reviewing a site before release

Maintainers diagnosing responsive or consistency regressions

BEFORE YOU USE IT

Risks to review before use

High

Unintended changes during remote review

Browser actions or source edits against a production target can alter data or broaden the change. Keep production review read-only, confirm the source workspace, and test fixes locally.

SECURITY

What the permission profile means

  • Use test accounts and avoid capturing secrets or personal data in screenshots.
  • Keep source modifications scoped to the reviewed issue.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked
references/visual-checklist.mdUpstream package contentSource-linked
references/framework-fixes.mdUpstream package contentSource-linked

TAGS

design-reviewresponsivevisual-qa

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit 318066d2, checked 2026-08-20; not independently executed or security-certified.