---
name: frontend-release-check
description: Produce a scoped release review with source evidence and a separate runtime verification queue.
---

# Frontend release check

Use this skill when asked to review a frontend release or supplied HTML for observable defects. Adapt the review to the available artifacts: source-only inspection and browser execution produce different evidence and must be reported separately.

## Inputs and scope
Identify the changed page, intended user tasks, acceptance criteria, and available source or running URL. Read supplied HTML, CSS, and relevant scripts before choosing checks. If only a snippet exists, constrain conclusions to that snippet. Do not start servers, install packages, access accounts, or deploy unless these actions are within the user's request and host permissions.

## Workflow
Trace each primary task from its visible control to its destination or handler. Check labels and accessible names, internal fragment targets, form relationships, document structure, and explicit metadata. For each issue, cite a file and line or stable input identifier, describe a concrete user consequence, and suggest a minimal correction. Prioritize broken primary actions above cosmetic preferences.

When browser access is available, test keyboard operation, focus visibility, responsive overflow, and the actual task result. Record viewport, browser, interaction, and observed outcome. Without browser execution, create a runtime queue for these checks; do not infer working interactions, contrast ratios, or layout from attractive source code. An empty alternative text is not automatically a defect: determine whether the image communicates meaning or is decorative.

## Output contract
Return evidence mode, findings with severity and locators, checks that passed within that mode, and remaining release checks. A source review does not establish production readiness. Keep fixes as recommendations unless editing was requested. Before delivery, distinguish defects proved by the available artifact from risks needing runtime evidence, and ensure no successful browser checks or measurements were invented.