---
name: compot-swiftui-review
description: Review one SwiftUI change against its intended user behavior using a review worksheet. Use for a focused code review with explicit evidence, reproduction steps, and coverage limits; pair with specialist guidance for framework details.
license: MIT
metadata:
  author: Lukáš Soukup
  version: "1.0.0"
---

# Compot SwiftUI review worksheet

Use this workflow for a scoped review. It organizes the evidence for a finding;
it does not supply a comprehensive SwiftUI API or modernization checklist.

## Establish the review boundary

Identify the changed feature, the expected user outcome and the relevant
callers. Check the project's instructions, deployment targets, build settings
and available verification tools. Record missing context before drawing a
conclusion that depends on it.

Open [the worksheet](references/review-worksheet.md) for the output fields and
evidence labels. Read [the exercise](references/review-exercise.md) when an
example helps distinguish a behavioral defect from a product-policy question.

## Trace a candidate finding

Choose a concrete action or state transition and follow it through the code.
Locate the value or side effect responsible for the observed or predicted
result. Compare that result with the feature's stated behavior.

Try to disprove the concern: inspect the caller, an existing guard, ownership
of the edited value and any relevant test. Use version-matched official docs
or an available specialist skill for uncertain framework semantics. Cite the
evidence that changes the conclusion. Do not treat a general coding preference
as the product's contract.

## Return an actionable review

Report each supported defect using the worksheet. State whether its trigger
was executed or inferred from source, and record the meaningful verification
that remains. Rank it by the consequence and realistic conditions of use.

When information is insufficient, identify the missing requirement or check
as an open question. If there are no supported findings, say so and describe
the review's coverage. Do not manufacture a finding to fill an output format.

Keep the review read-only unless the task already authorizes fixes. This skill
does not authorize uploads, production writes or public distribution.