caliber-onboarding — Claude Code rule: check config sync status
caliber-onboarding — a rule for Claude Code and Codex that checks whether Caliber configs are synced before the agent responds to your first message. If sync is not set up, it offers to run /setup-caliber in about 30 seconds.
MIT ★ 1,319 updated 2026-09-24
.claude/rules/caliber-onboarding.mdWhat caliber-onboarding does
On both Claude Code and Codex, the rule runs before the agent's first response. It checks for caliber inside the pre-commit hook — if missing, it notifies you of desync and asks whether to run automatic setup. If the hook already contains caliber, the rule stays silent and proceeds normally. When you agree to install, /setup-caliber takes roughly 30 seconds, then the agent handles your original request.
This rule matters when your team uses the same Caliber setup or you develop across multiple machines: it keeps your local configs aligned with the central store so no one drifts out of sync.
What it helps with
- verify Caliber configs are synced when you start a session
- remind you to set up Caliber if it is missing from the project
- trigger automatic sync with a single command
- prevent config drift across developers or machines
Example prompts for the agent
- Open your project in Claude Code — the rule checks sync status before your first message
- If you see a desync notice, confirm the
/setup-calibercommand or skip it to proceed - Once installed, the rule stops alerting you after each session restart
How to install caliber-onboarding
Manually: put the files in place
.claude/rules/caliber-onboarding.mdThe paths frontmatter field limits the files
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/caliber-onboarding.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.github/instructions/caliber-onboarding.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.devin/rules/caliber-onboarding.mdManually: put the files in place
.clinerules/caliber-onboarding.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about caliber-onboarding
How do I install caliber-onboarding in Claude Code?
Place the file caliber-onboarding.md in .claude/rules/. The rule activates automatically when you start your next session.
What does caliber-onboarding do?
It checks whether Caliber sync is set up via the pre-commit hook. If not, it suggests running /setup-caliber to configure your project's agents in seconds.
Which IDEs and editors support this rule?
This version runs on Claude Code and Codex. Alternative files exist for Cursor (.cursor/rules/), GitHub Copilot (.github/instructions/), Windsurf (.devin/rules/), and Cline (.clinerules/).
Source text
caliber-onboarding.md · MIT
# Caliber Setup Check At the very start of each session, before responding to the user's first message, run this command: ```bash grep -q "caliber" .git/hooks/pre-commit 2>/dev/null && echo "SYNCED" || echo "NOT_SYNCED" ``` If the result is NOT_SYNCED, tell the user: "This project uses Caliber to keep agent configs in sync — it is not set up yet. Want me to run /setup-caliber? (~30 seconds)" If they agree, run /setup-caliber. Then proceed with their original request. If they decline, proceed normally. If SYNCED, say nothing and proceed normally.
© caliber-ai-org · MIT · caliber-ai-org/ai-setup