consult-claude

Launch Claude Code as an independent reviewer in a sealed repository snapshot.

4.8k|376|Updated Mar 16, 2023
One-click install
npx skills add https://github.com/EpicenterHQ/epicenter --skill consult-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consult-claude
Source: https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/consult-claude
Command: npx skills add https://github.com/EpicenterHQ/epicenter --skill consult-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Getting a second opinion on code or research usually means pasting snippets into a chat, losing repository context, or risking an external agent mutating your live checkout. This Skill runs Claude Code against an isolated, editable replica of your repository so it can investigate, experiment, and report back without touching your working tree.

Core Features & Use Cases

  • Sealed laboratory snapshots: Clones the current repository state (including uncommitted changes and untracked files) into an independent replica with the Git remote removed and network egress disabled.
  • Checkpoint-based reporting: Claude writes structured checkpoints (state: working, needs-decision, or complete) that you can poll without interrupting the running session.
  • Follow-up conversations: Continue the same laboratory session after a decision checkpoint, archiving prior results, or start a fresh snapshot when the live checkout has moved on.
  • Use Case: Ask Claude to independently review a proposed storage-layer refactor; it runs tests and commits experiments in its replica while you keep working, then returns a recommendation with cited evidence.

Quick Start

Ask the assistant to consult Claude about your design question and wait for its checkpointed recommendation before deciding what to change.

Frequently Asked Questions about consult-claude

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

FAQPage Schema
How do I run Claude Code as an independent code reviewer?

Run the consult-claude start command from the repository root with a research brief piped via stdin. It clones your repo into a sealed replica, launches a background Claude session there, and prints a run ID you can poll for checkpoint results.

How to get a second AI opinion without changing my working repository?

Use a snapshot-based consultation: the script copies HEAD, uncommitted diffs, and untracked files into an independent clone with the Git remote removed. Claude edits and commits only inside that replica, so your living checkout is never modified.

Can Claude access the network during a consultation run?

No. The laboratory settings enforce a sandbox with an empty network allowlist and deny WebFetch, so Bash network egress is offline. Claude may use WebSearch, but any direct fetching or external action is treated as a deliberate escalation outside the default run.

How do I continue a Claude research session after a checkpoint?

Use the follow-up command with the run ID once the checkpoint shows state needs-decision or complete. The runner archives the prior checkpoint, resumes the same native Claude session, and optionally waits for the next terminal checkpoint.

What are the limitations of snapshot-based AI code review?

Each checkpoint is tied to one snapshot, so claims cannot be re-verified against a checkout that has since changed. When live work has materially moved on, you must start a new laboratory snapshot rather than refreshing the worker's replica.