council-router

Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.

$ 설치

git clone https://github.com/namastexlabs/automagik-genie /tmp/automagik-genie && cp -r /tmp/automagik-genie/.claude/skills/council-router ~/.claude/skills/automagik-genie

// tip: Run this command in your terminal to install the skill


name: council-router description: Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.

Council Router

Routes reviews to specialized council members based on code context.

When to Invoke Council

  • PR reviews with significant changes
  • Architecture decisions or design proposals
  • New dependency additions
  • Security-sensitive code modifications
  • Performance-critical path changes
  • API surface changes

Routing Rules

ContextRoute ToWhy
Security-sensitive code (auth, crypto, input validation)@sentinelTroy Hunt mindset - security-first
Performance-critical paths (hot loops, data processing)@benchmarkerMatteo Collina - measure everything
New dependencies or abstractions@questionerRyan Dahl - challenge assumptions
API changes (public interfaces, CLI)@ergonomistSindre Sorhus - DX obsession
Deployment configs (Docker, K8s, CI/CD)@operator, @deployerKelsey + Guillermo - ops reality
Observability code (logging, metrics, tracing)@measurer, @tracerBryan + Charity - production debugging
Architecture decisions (module boundaries, patterns)@architectLinus - systems thinking
Complex abstractions (over-engineering risk)@simplifierTJ - elegant minimalism

Usage

When a review context matches multiple categories, invoke multiple council members. Each member votes: APPROVE, REJECT, or MODIFY with rationale.

Agent Aliases

All council members are available as Claude agents:

  • @questioner, @benchmarker, @simplifier
  • @sentinel, @ergonomist, @architect
  • @operator, @deployer, @measurer, @tracer