---
name: submit-change-step
description: Use when code edits are complete in a Remix-bound repo and the work should be recorded as a Remix change step.
---

# Submit Remix Change Step

Use this skill after edits are complete and the task should be captured as the final recorded turn in a Remix-bound repo.

This skill is specifically about what `remix_collab_finalize_turn` needs to record the completed work correctly.

Workflow:

1. Run `remix_collab_status` first to confirm the repo is bound and inspect current warnings.
2. Use `remix_collab_finalize_turn` before the final response, with the exact user prompt and your final assistant response.
3. Let `remix_collab_finalize_turn` choose the changed-turn path from the live worktree by default.
4. Provide an explicit external diff only when the task requires recording a diff that is not present in the current worktree.

Important behavior:

- `remix_collab_finalize_turn` is the authoritative recording path for completed work instead of raw git commit or push.
- When the diff comes from the live worktree, Remix may discard tracked changes and captured untracked paths locally as part of auto-sync.
- When the diff comes from an external source, automatic local discard+sync is skipped because the external diff may not match the current worktree.
- The resulting git commit is created on the Remix side first and appears in the local repo after sync or auto-sync.
- Surface these side effects clearly to the user when they matter.
- If the user wants to understand current repo state before recording, re-run `remix_collab_status`.
- Do not make further repo mutations after the final recording call unless you intend to record another completed turn.
- If `remix_collab_finalize_turn` reports that the change step succeeded remotely but local sync failed, do not retry finalize immediately.
- In that recovery case, treat the tool's `recommendedNextActions` and `error.hint` as authoritative, starting with `remix_collab_status`, then `remix_collab_sync_preview`, then `remix_collab_sync_apply` when appropriate.
- If the error surfaces a preserved diff backup path, mention it explicitly and preserve it as the fallback recovery artifact while you repair local sync state.

Use external diff input only when the task explicitly requires it. Otherwise prefer the current worktree.
