# /occhio

Run an Occhio UI quality review for the current repository.

## Goal
Catch accessibility, consistency, and UX-pattern regressions before PR review.

## Workflow
1. Scope the review to the files the user named. If no scope is provided, prioritize recently changed UI files.
2. If the local CLI is available, run `occhio scan --format json` and use those results as the primary signal.
3. If the CLI is unavailable, perform a static review with the same categories and note that CLI checks were not run.
4. Report findings by severity with exact file paths and line numbers.
5. For each finding, include why it matters and a concrete fix.

## Findings Format
- Summary: short status line.
- Accessibility findings
- Consistency findings
- UX-pattern findings
- Suggested code changes

If no issues are found, state that clearly and list any residual risk (for example: dynamic runtime states not validated).