local-cerebro

Delegates code-level questions about indexed repositories to a local cerebro CLI without checking them out.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bearded-giant/claude-code-config --skill local-cerebro-bearded-giant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-cerebro
Source: https://github.com/bearded-giant/claude-code-config/tree/main/skills/local-cerebro
Command: npx skills add https://github.com/bearded-giant/claude-code-config --skill local-cerebro-bearded-giant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When you need code-level answers about repositories that are not checked out in your current session, cloning or browsing them manually pollutes your working context. This Skill forwards the question to a locally running cerebro instance that has those repos indexed, returning the answer on stdout while keeping your session uncluttered. ## Core Features & Use Cases - One-shot repo Q&A: Ask code-level questions about indexed repos (frost, customcheckout, event-bus, recharge-foundations) via a single script call, with answers returned on stdout. - Readiness preflight: The script checks the cerebro directory, uv, .env, API key, and indexed repo count before invoking, printing a status report and exiting with code 3 if cerebro is not ready. - Model selection and billing control: Choose haiku, sonnet, or opus per call, and set ANTHROPIC_API_KEY to bill a platform key instead of the logged-in subscription. - Use Case: While working in one service, ask "what does frost do for webhook retries, cite files" and get a cited answer without checking out the frost repo. ## Quick Start Ask cerebro what the frost repo does for webhook handling and request file citations in the answer.

Frequently Asked Questions about local-cerebro

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

FAQPage Schema
How do I ask questions about a repo I don't have checked out?

Run the cerebro-ask.sh script with a prompt that names the repo, for example a question about frost or customcheckout. The local cerebro instance resolves the repo from its indexed project map and returns the answer on stdout.

How do I check if local cerebro is ready to answer questions?

Run cerebro-ask.sh with the status argument. It reports whether the cerebro directory, uv, .env, and API key are present plus the indexed repo count, exiting 0 when ready and 3 when not ready.

Can I choose which Claude model answers the cerebro query?

Yes, pass haiku, sonnet, or opus as the second argument to cerebro-ask.sh. The default model is opus, and invalid model names fall back to opus with a warning on stderr.

Why does the cerebro call exit with code 3?

Exit code 3 means cerebro is not ready: the cerebro directory or broker/cli.py is missing, or uv is not installed. The script prints a full status report to stderr so you can fix the setup before retrying.

Can cerebro edit or commit code in the indexed repos?

No, cerebro operates read-only and rejects build or write attempts with exit code 2. The calling session owns all commits, since cerebro only reads its indexed checkouts on whatever branch they are on.