/ Каталог / Песочница / Carmack-Council
← Все серверы ↗ GitHub
● Сообщество SamJHudson01 ⚡ Сразу

Carmack-Council

автор SamJHudson01 · SamJHudson01/Carmack-Council

Multi-agent Claude Code framework: 10 expert sub-agents (Carmack, Fowler, Kent Beck, Troy Hunt...) each review code in parallel with their own 200k context.

The Carmack Council structures development as spec → plan → implementation → review, with feedback loops. The headline innovation is parallel expert subagents: the Chair orchestrator dispatches 10 specialists simultaneously (Carmack engineering, Fowler refactoring, Kent Beck testing, Troy Hunt security, Matteo Collina backend, Brandur Postgres, Vercel perf, Simon Willison LLMs, Karri Saarinen UI, Vitaly Friedman UX). Each gets its own 200k context for its domain.

▶ Смотреть демо 📦 Установить 💡 Сценарии

Зачем использовать

Ключевые функции

Живое демо

Как выглядит на практике

carmack-council-skill.replay ▶ готово
0/0

Установка

Выберите клиент

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "carmack-council-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ],
      "_inferred": true
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "carmack-council-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/SamJHudson01/Carmack-Council",
        "~/.claude/skills/Carmack-Council"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json
{
  "context_servers": {
    "carmack-council-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/SamJHudson01/Carmack-Council",
          "~/.claude/skills/Carmack-Council"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add carmack-council-skill -- git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: Carmack-Council

Get a 10-expert review on a PR before you merge it

👤 Engineers on small teams without a deep review bench ⏱ ~30 min intermediate

Когда использовать: You'd like a security person, a perf person, a testing person to look at your PR — but there's just you.

Предварительные требования
  • Skill cloned — git clone https://github.com/SamJHudson01/Carmack-Council ~/.claude/skills/Carmack-Council
Поток
  1. Invoke the review stage
    Carmack Council review: PR <link or diff>. Dispatch all experts.✓ Скопировано
    → Ten parallel reviews running, each domain-scoped
  2. Read the merged report
    Summarize the top 3 issues across all experts, ordered by severity.✓ Скопировано
    → Prioritized, not 10 disjoint reports
  3. Fix and re-review
    I fixed 1 and 2. Re-review with just Troy Hunt and Brandur for issue 3.✓ Скопировано
    → Focused re-review, not full re-dispatch

Итог: A PR that's survived 10 expert lenses — stronger than a rubber stamp from a teammate.

Подводные камни
  • Experts disagree — The Chair merges and prioritizes — if two experts conflict, pick the one your situation weights heavier
Сочетать с: github

Run a feature through the full spec → plan → implement → review pipeline

👤 Small teams building a feature end-to-end with AI ⏱ ~120 min advanced

Когда использовать: Feature is substantial and you want structured gates.

Поток
  1. Spec
    Carmack Council: spec for adding Stripe-based subscriptions.✓ Скопировано
    → Carmack-opinionated spec — pragmatic, not architecture-astronautic
  2. Plan + implement
    Proceed to plan, then implement in the smallest vertical slice.✓ Скопировано
    → Thin working slice, not a scaffolding swamp
  3. Council review
    Review with all 10 experts.✓ Скопировано
    → Cross-domain findings tied to actual lines

Итог: A feature shipped with a thoroughly reviewed implementation.

Подводные камни
  • You treat expert style as gospel — They're opinions backed by real engineers' writing — they're evidence, not commandments
Сочетать с: github · planning-with-files

Комбинации

Сочетайте с другими MCP — эффект x10

carmack-council-skill + github

Run council_review against a real PR, post summary as a PR comment

Council review PR #47; post the prioritized top-5 as a comment.✓ Скопировано
carmack-council-skill + planning-with-files

Track council findings across multiple review rounds

Use planning-with-files progress.md to track which council findings are resolved.✓ Скопировано

Инструменты

Что предоставляет этот MCP

ИнструментВходные данныеКогда вызыватьСтоимость
spec_stage feature intent Start of a feature 0
plan_stage approved spec After spec 0
implement_stage approved plan Actually building 0
council_review diff or PR Before merge High — 10 parallel agents
single_expert_review diff + expert name Re-check a specific concern after fix 1/10 of full council

Стоимость и лимиты

Во что обходится

Квота API
None
Токенов на вызов
High — council_review runs 10 parallel agents
Деньги
Free — skills are local files. LLM token cost scales with parallelism.
Совет
Use single_expert_review for targeted re-checks; full council is expensive per run.

Безопасность

Права, секреты, радиус поражения

Хранение учётных данных: No credentials — pure prompts
Исходящий трафик: None — all review happens in-session

Устранение неполадок

Частые ошибки и исправления

Skill not invoked — Claude does a regular review

Say 'Carmack Council review' explicitly.

Проверить: ls ~/.claude/skills/Carmack-Council/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives dispatch logic.

Проверить: head ~/.claude/skills/Carmack-Council/SKILL.md
Wrong trigger keywords — only one expert activates

Say 'dispatch all experts' or 'full council' explicitly.

Альтернативы

Carmack-Council в сравнении

АльтернативаКогда использоватьКомпромисс
Single-reviewer vanilla ClaudeSmall changes where 10 experts is overkillCheaper, less coverage
Human code reviewTeam has real reviewersBetter but slower — Council complements, doesn't replace

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills