agents-consilium

Featured

Run external coding agents (Codex, Claude Code, OpenCode, native Grok Build, Gemini) as independent reviewers, stateful repository researchers, or single-agent implementers. Use for multi-model opinions and code review, steerable Grok research, full-access delegation, long-running work, or reattaching to delegated runs. Not for simple questions answerable directly from docs or the current codebase.

AI & Automation 149 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Agents Consilium Resolve the entrypoint below, then use only `"$CONSILIUM"`. Select the mode from the user's intent and load only the linked reference needed for that mode. ## Entrypoint resolution Set `CONSILIUM` to the `consilium` executable in the `scripts` subdirectory of the exact `SKILL.md` loaded by skill discovery. Verify it before the first call: ```bash test -x "$CONSILIUM" || { echo "agents-consilium entrypoint not found: $CONSILIUM" >&2; exit 1; } ``` Resolve this from the loaded skill path, never from the caller's working directory, repository root, or `PATH`. Do not execute the entrypoint as a relative path. Keep the shell in the repository the external agent should inspect or change. ## Prompt transport is part of the launch Every `review ask` invocation must visibly transport a non-empty prompt in the same shell command: as the positional argument, through an explicit stdin pipe or heredoc, or with `--prompt-file FILE`. Never run a bare `review ask` command with only options and assume that prompt text from commentary, planning, or the surrounding agent context becomes stdin; shell execution has no such implicit connection. For a generated multiline repository review, prefer an explicit heredoc or prompt file so the complete problem statement and context seed are delivered atomically. ## Recommended review defaults Use these unless the user asks for a different tradeoff: - Independent architecture, design, debugging, or planning opinions: `review a...

Details

Author
CodeAlive-AI
Repository
CodeAlive-AI/ai-driven-development
Created
8 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

consilium

Run a consilium - a structured multi-model review of a technical question or design decision. Independent reviewers (Claude, Codex, Open Code and others) each write a review of the same brief, arbiters merge them into a draft decision, and after the user confirms it an implementer makes the authorized changes and verifiers check them. Use ONLY when the user explicitly asks for a consilium, a multi-model review or a second opinion from several models; it sends project files to several model providers and can take many minutes.

1 Updated 6 days ago
kavyrshin
AI & Automation Listed

second-agent

Get a second opinion, code review, or delegate a task (write code, fix a bug, refactor) to Gemini, opencode, Codex, Claude Code, Copilot, Qwen, Kilo, Antigravity (agy), Command Code (cmd), Cursor, or Kiro CLI. Covers generic requests ("a second opinion", "another perspective", "independent review", "cross-model review") and engine-named ones ("ask Gemini", "codex review", "use opencode", "have Cursor fix this", "Qwen's take", "ask Copilot", "agy review", "cmd review", "kilo's take", "ask kiro-cli", "Claude review"). Named engine → use it directly. Unnamed → ask once, with a recommended default.

0 Updated 1 months ago
srwbsw
Code & Development Listed

code-review

Multi-agent code review with parallel specialized reviewers, architecture validation, challenge validation, and durable handling of previously decided findings. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before applying fixes or adding decision comments.

46 Updated 1 months ago
martinffx