Check sync, capabilities, and repository status¶
Run these checks before a cross-repository change and after changing shared agent context.
Execution status
On pull requests, main pushes, and the weekly Spine checks, CI regenerates
agent configuration, verifies idempotence, and runs repository-status unit
tests. It does not run doctor.sh against a contributor's installed tools
or inspect their live checkouts; those two checks remain manual.
Synchronize generated agent configuration¶
The first command regenerates local Claude, Codex, and Cursor surfaces from tracked sources. The second verifies idempotence. Generated instruction and editor trees are not the source of truth; see source ownership.
Check active capabilities¶
The doctor distinguishes hard failures from optional or one-time warnings and
continues through every check. Use --strict only when warnings must also make
the command fail.
Inspect repository state¶
The JSON output reports branch, dirty counts, upstream divergence, stashes, linked worktrees, and the impact of switching to the target. Resolve unexpected changes before using checkout or pull procedures. The status command is read-only; it does not switch branches.
For a compact lookup of these and related commands, use the command reference.