---
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 a Remix collaboration step.

In a Remix-bound repo, `remix_collab_add` is the authoritative Remix recording path for completed work instead of raw git commit or push.
If the tool list is ambiguous, prefer the clearer alias `remix_collab_add_change_step` for manually recording a code-diff change step.
It creates the next commit on the Remix side from the submitted diff, then syncs the local repo to that new commit when auto-sync succeeds.

In this plugin setup, the preferred default is automatic end-of-response recording:

- if the completed assistant response produced a repo diff, the hook records exactly one `remix_collab_add`
- if the completed assistant response produced no repo diff, the hook records one `remix_collab_record_turn` instead

Workflow:

1. Run `remix_collab_status` first to confirm the repo is bound and inspect current warnings.
2. If the repo is not bound, stop and ask whether to initialize with `remix_collab_init`.
3. Do not proactively call `remix_collab_add` during ordinary work.
4. Only use `remix_collab_add` when the user explicitly asks for a manual recording step, or when doing operational recovery, backfills, or debugging.

Important behavior:

- `remix_collab_add` defaults to auto-sync behavior in this Remix setup.
- `remix_collab_record_turn` is for no-diff prompt/response history only and should not be used when the worktree has code changes.
- During ordinary work, the hook is the normal automatic path for changed-turn recording.
- In the automatic hook path, the `remix_collab_add` prompt is the exact user prompt for that completed turn.
- The automatic hook may also attach the final assistant response so changed turns and no-diff turns share the same prompt/response chronology.
- Do not use raw `git commit` or `git push` as collaboration-recording steps in a bound repo.
- If automatic recording cannot complete safely, recover through Remix status, sync, reconcile, and manual recording flows rather than local git mutation.
- When the diff comes from the live worktree, Remix may discard tracked changes and captured untracked paths locally as part of auto-sync.
- 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`.

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