bicameral-doctor

Detect drift between decisions and code across file or branch scopes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bicameral-doctor
Source: https://github.com/BicameralAI/bicameral-mcp/tree/main/.claude/skills/bicameral-doctor
Command: npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Automates drift health checks by automatically selecting the appropriate scope (file or branch) based on user input, surfacing drift, grounding status, and actionable guidance.

## Core Features & Use Cases

  • Auto scope selection: file vs branch depending on input
  • Drift detection and repository ledger health across the codebase
  • Guidance for grounding decisions and sign-off workflows
  • Preflight health checks integrated with code reviews

### Quick Start Ask Bicameral Doctor to run a health check with bicameral.doctor() to scan the current workspace.

Frequently Asked Questions about bicameral-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect code drift between decisions and my repository?

Drift detection evaluates repository changes on file or branch scope, comparing the codebase against a decision ledger to surface drifted, ungrounded, and pending decisions along with a repo-wide summary.

What is the difference between file scope and branch scope for drift health checks?

File scope evaluates drift for individual files, while branch scope executes a branch-wide sweep. The health check automatically selects the appropriate scope based on your input to surface ungrounded decisions.

How do I run a preflight health check for code reviews?

Run a health check scan on your current workspace to evaluate repository ledger health. This preflight scan integrates with code reviews to produce actionable hints for grounding decisions and sign-off workflows.

Do I need a decision ledger to use automated drift detection?

Yes, automated drift detection requires access to the repository's decision ledger. It uses this ledger to evaluate changes, identify drifted decisions, and generate actionable guidance for sign-off.

What is the best way to surface ungrounded decisions across a codebase?

The best way to surface ungrounded decisions is running a branch-wide sweep health check. This scans the entire codebase against the decision ledger to automatically produce a repo-wide ledger summary.