sync Command
What It’s For
Section titled “What It’s For”Reconcile workspace state when repositories drift or after branch lifecycle changes.
What It Does
Section titled “What It Does”- Checks configured repositories against expected workspace metadata.
- Refreshes repository/worktree alignment.
- Surfaces mismatches so maintainers can resolve them quickly.
arashi sync [options]Key Options
Section titled “Key Options”--only <repos>sync comma-separated repository names only.-v, --verboseshow detailed per-repository sync output.--jsonoutput machine-readable sync results.
Examples
Section titled “Examples”# Sync all managed repositoriesarashi sync
# Sync selected repositoriesarashi sync --only api,web
# Sync with per-repo detailsarashi sync --verbose
# Sync selected repositories and emit JSONarashi sync --only api,web --jsonsyncaligns repositories to the parent repository’s current branch.- When needed, it can create missing target branches in child repositories.
- JSON mode keeps stdout parseable as a single result document for programmatic callers.
Agent Notes
Section titled “Agent Notes”- Use
arashi syncwhen branch/worktree state has drifted and you need the child repos aligned to the current parent branch. - Inspect
arashi statusbefore and after sync so any remaining mismatches are visible before implementation or handoff. - Avoid using sync as a substitute for understanding dirty worktrees; resolve or preserve local changes deliberately.