---
name: review-save-flow
description: Review a React Native save flow for repeated requests and retry after failure. Use when explicitly asked to review save/submission concurrency. Report evidence and limits; do not edit code.
---

# Review a save flow

Read the task requirements, project context and the exact files the user names. Limit the review to the supplied save flow. If code or a required command is unavailable, state what could not be checked.

## Procedure

1. Identify which object owns the in-flight state and how long it lives. Inspect where the gate is created and where it is called.
2. Follow two calls made before the first settles. Determine whether a second task starts. Check that admission changes synchronously before awaiting work.
3. Follow success, rejection and a synchronous throw. Check whether the owner can try again. A finally block can release the gate; its mere presence is not proof that it releases the right state.
4. Inspect caller-facing errors and the UI integration. Busy state and button disabling support the interaction; they do not establish server idempotency.
5. Use project-provided tests where available. Read the test command before running it. Report the actual command and result. When execution is unavailable, label the conclusion as code review.
6. In a guided teaching review, compare against `cases.md` when it is supplied as reference material. In a blind evaluation, do not open the answer key or request it; review only the supplied inputs. Intentional failure fixtures are learning cases. Read context before calling every matching token a bug.

## Findings format

For each supported issue provide file and line, the triggering sequence, expected behavior, observed code path, likely effect and the smallest corrective suggestion. Separate confirmed code findings, hypotheses requiring runtime checks, and inspected cases that appear correct.

Finish with commands actually run and the review's limits. When no supported issue is found, say so with the reviewed scope. Do not generate an arbitrary finding count. Do not modify files or claim device validation, server guarantees or universal safety.