llm-council
SolidUse when a pr-council-review (PR or branch mode) result needs independent corroboration from a different model family before trusting a GREEN verdict — high-stakes, security-sensitive, or architecturally significant reviews where same-model-family Claude subagents might share a blind spot. Also use when the user asks for "external", "second opinion", "cross-model", or names codex/antigravity (`agy`) or another external CLI coding agent alongside a review.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- ffroliva
- Repository
- ffroliva/gflow-cli
- Created
- 3 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
pr-council-review
Multi-dimensional LLM council review of an open PR (default) or a local feature branch (§ 8 branch mode, invoked via `/gflow:branch-review`). Five baseline dimensions (correctness, quality, security, tests, memory-hygiene) plus adaptive dimensions per surface (transports / data / CLI / docs / auth / BDD / scripts / release-gate). Each agent invokes specialized skills (security-review, code-review, verify) for its dimension. Reads files via `git show <sha>:<path>` to avoid stale-working-tree false positives. Cross-tool portable.
council
Gathers N independent, decorrelated perspectives across model families (external CLIs when present, subagents when not) and arbitrates inline. Use when a decision needs genuine debate — not same-model echo — for critique, review, or judge calls. Honest about degradation: never claims 'consensus' from a single model family.
llm-council
Run a decision through a council of five advisors who analyze it independently, peer-review each other anonymously with a forced ranking, and get synthesized into one verdict. Adapted from Andrej Karpathy's LLM Council. MANDATORY TRIGGERS - "council this", "run the council", "war room this", "pressure-test this", "stress-test this", "debate this". STRONG TRIGGERS when paired with a real tradeoff - "should I X or Y", "which option", "what would you do", "is this the right move", "validate this", "get multiple perspectives", "I can't decide", "I'm torn between". Do NOT trigger on factual lookups, creation tasks ("write me a tweet"), processing tasks ("summarize this"), or a casual "should I" with no meaningful tradeoff. DO trigger when there is genuine uncertainty, more than one defensible option, and a real cost to being wrong.