# ckb-sync-changes — edge cases Reference material for the `ckb-sync-changes` skill. Read when a run hits an unusual situation the main steps don't cover. - **Nothing to do on either side** — report "already in sync," make no commits, run no push. - **Local changes only, remote unchanged** — commit, fast-forward push, no merge/conflict step needed. - **Remote changes only, local clean** — fast-forward merge, nothing to commit, nothing to push; report "pulled N commits, nothing local to push." - **Push rejected twice in a row** — stop, report the raw git error, do not force and do not retry a third time. - **No `origin` remote configured** — handled proactively in Step 2 (ask the user for the URL and add it), not treated as a failure. - **User pastes an invalid or unreachable URL** — `git remote add` itself usually still succeeds (it doesn't validate reachability); the failure surfaces at the `git fetch origin` in Step 3. Report that raw error and ask the user to confirm the URL rather than guessing a correction. - **Fetch/push fails on auth/network once a remote is configured** — report the error clearly. This skill does not manage git credentials. --- *Licensed under the Apache License, Version 2.0 — see [LICENSE](../../../LICENSE) at the repository root, or .*