bicameral-sync
OfficialKeep the decision ledger current after commits.
System Documentation
What problem does it solve?
Full ledger sync after a git COMMIT — runs bicameral.link_commit then evaluates pending compliance checks to write reflected/drifted verdicts. ONLY for post-commit ledger sync. DO NOT trigger for "update", "upgrade", or "new version" requests — those belong to /bicameral:update (binary upgrade). Trigger on: PostToolUse hook "bicameral: new commit detected", _sync_guidance in any tool response, or explicit "sync", "check compliance", or reflect this commit".
Core Features & Use Cases
- Sync HEAD by running bicameral.link_commit to compute hash-level drift for the new commit.
- Resolve pending compliance checks by reading the code region, comparing the decision description against the code, and batching all verdicts into a single bicameral.resolve_compliance call.
- After resolution, report a summary such as Synced <short_hash>: N reflected · N drifted · N pending.
Quick Start
After a commit, run the bicameral-sync operation to complete the ledger by evaluating changed regions and writing verdicts.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: bicameral-sync Download link: https://github.com/BicameralAI/bicameral-mcp/archive/main.zip#bicameral-sync Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.