llm-cli-council 1.0.0

package/lib/platform-utils.sh

@@ -0,0 +1,353 @@
+#!/usr/bin/env bash
+# Platform Utilities for llm-cli-council
+# Cross-platform compatibility layer for macOS, Linux, and Windows/WSL
+
+set -euo pipefail
+
+# =============================================================================
+# Platform Detection
+# =============================================================================
+
+# detect_platform - Returns: macos, linux, windows, unknown
+# Usage: PLATFORM=$(detect_platform)
+detect_platform() {
+    local uname_s
+    uname_s=$(uname -s 2>/dev/null || echo "unknown")
+
+    case "$uname_s" in
+        Darwin*)
+            echo "macos"
+            ;;
+        Linux*)
+            # Check if running under WSL
+            if grep -qiE 'microsoft|wsl' /proc/version 2>/dev/null; then
+                echo "windows"
+            else
+                echo "linux"
+            fi
+            ;;
+        MINGW*|MSYS*|CYGWIN*)
+            echo "windows"
+            ;;
+        *)
+            echo "unknown"
+            ;;
+    esac
+}
+
+# =============================================================================
+# Timeout Command
+# =============================================================================
+
+# timeout_cmd - Execute command with timeout
+# Usage: timeout_cmd <seconds> <command> [args...]
+# Returns: Command exit code, or 124 on timeout
+timeout_cmd() {
+    local timeout_duration="$1"
+    shift
+
+    local platform
+    platform=$(detect_platform)
+
+    case "$platform" in
+        macos)
+            # Check for GNU timeout (from coreutils)
+            if command -v gtimeout &>/dev/null; then
+                gtimeout "$timeout_duration" "$@"
+            else
+                # Fallback: bash-only solution
+                _timeout_bash "$timeout_duration" "$@"
+            fi
+            ;;
+        linux|windows)
+            # Standard timeout command available
+            if command -v timeout &>/dev/null; then
+                timeout "$timeout_duration" "$@"
+            else
+                _timeout_bash "$timeout_duration" "$@"
+            fi
+            ;;
+        *)
+            # Unknown platform, try bash fallback
+            _timeout_bash "$timeout_duration" "$@"
+            ;;
+    esac
+}
+
+# _timeout_bash - Bash-only timeout implementation (fallback)
+_timeout_bash() {
+    local timeout_duration="$1"
+    shift
+
+    # Run command in background
+    "$@" &
+    local cmd_pid=$!
+
+    # Wait with timeout
+    local count=0
+    while kill -0 "$cmd_pid" 2>/dev/null; do
+        if [ "$count" -ge "$timeout_duration" ]; then
+            kill -TERM "$cmd_pid" 2>/dev/null || true
+            sleep 0.5
+            kill -KILL "$cmd_pid" 2>/dev/null || true
+            return 124
+        fi
+        sleep 1
+        ((count++)) || true
+    done
+
+    # Get exit code
+    wait "$cmd_pid"
+}
+
+# =============================================================================
+# Process Management
+# =============================================================================
+
+# wait_for_pid - Wait for a process to complete with timeout
+# Usage: wait_for_pid <pid> <timeout_seconds>
+# Returns: 0 if process completed, 1 if timeout
+wait_for_pid() {
+    local pid="$1"
+    local timeout="${2:-30}"
+    local count=0
+
+    while kill -0 "$pid" 2>/dev/null; do
+        if [ "$count" -ge "$timeout" ]; then
+            return 1
+        fi
+        sleep 1
+        ((count++)) || true
+    done
+
+    return 0
+}
+
+# =============================================================================
+# Temporary Files and Directories
+# =============================================================================
+
+# make_temp_file - Create temporary file
+# Usage: TEMP_FILE=$(make_temp_file [prefix])
+make_temp_file() {
+    local prefix="${1:-tmp}"
+    local platform
+    platform=$(detect_platform)
+
+    case "$platform" in
+        macos)
+            mktemp -t "${prefix}.XXXXXX"
+            ;;
+        linux|windows)
+            mktemp -t "${prefix}.XXXXXX"
+            ;;
+        *)
+            # Fallback: manual temp file creation
+            local temp_file="/tmp/${prefix}.$$.$RANDOM"
+            touch "$temp_file"
+            echo "$temp_file"
+            ;;
+    esac
+}
+
+# make_temp_dir - Create temporary directory
+# Usage: TEMP_DIR=$(make_temp_dir [prefix])
+make_temp_dir() {
+    local prefix="${1:-tmp}"
+    local platform
+    platform=$(detect_platform)
+
+    case "$platform" in
+        macos)
+            mktemp -d -t "${prefix}.XXXXXX"
+            ;;
+        linux|windows)
+            mktemp -d -t "${prefix}.XXXXXX"
+            ;;
+        *)
+            # Fallback: manual temp dir creation
+            local temp_dir="/tmp/${prefix}.$$.$RANDOM"
+            mkdir -p "$temp_dir"
+            echo "$temp_dir"
+            ;;
+    esac
+}
+
+# =============================================================================
+# JSON Parsing
+# =============================================================================
+
+# json_get - Simple JSON value extraction
+# Usage: json_get <json_file> <key>
+# Example: json_get config.json ".providers[0].name"
+# Note: Requires jq if available, otherwise uses grep/sed fallback
+json_get() {
+    local json_file="$1"
+    local key="$2"
+
+    if ! [ -f "$json_file" ]; then
+        echo "Error: JSON file not found: $json_file" >&2
+        return 1
+    fi
+
+    # Try jq first (most reliable)
+    if command -v jq &>/dev/null; then
+        jq -r "$key // empty" "$json_file" 2>/dev/null || echo ""
+        return 0
+    fi
+
+    # Fallback: grep + sed (limited, but works for simple keys)
+    # This only handles simple cases like: {"key": "value"}
+    # Does NOT handle nested objects or arrays reliably
+    local simple_key
+    simple_key=$(echo "$key" | sed 's/^\.//; s/\[.*\]//g')
+
+    grep -o "\"$simple_key\"[[:space:]]*:[[:space:]]*\"[^\"]*\"" "$json_file" 2>/dev/null \
+        | head -1 \
+        | sed 's/.*:[[:space:]]*"\([^"]*\)".*/\1/' \
+        || echo ""
+}
+
+# json_has_key - Check if JSON file contains a key
+# Usage: json_has_key <json_file> <key>
+# Returns: 0 if key exists, 1 otherwise
+json_has_key() {
+    local json_file="$1"
+    local key="$2"
+
+    if ! [ -f "$json_file" ]; then
+        return 1
+    fi
+
+    if command -v jq &>/dev/null; then
+        jq -e "$key" "$json_file" &>/dev/null
+        return $?
+    fi
+
+    # Fallback: simple grep
+    local simple_key
+    simple_key=$(echo "$key" | sed 's/^\.//; s/\[.*\]//g')
+    grep -q "\"$simple_key\"" "$json_file" 2>/dev/null
+}
+
+# =============================================================================
+# Path Resolution
+# =============================================================================
+
+# path_resolve - Resolve path with tilde expansion and environment variables
+# Usage: RESOLVED=$(path_resolve "~/path/to/file")
+path_resolve() {
+    local path="$1"
+
+    # Expand tilde
+    if [[ "$path" =~ ^~ ]]; then
+        path="${path/#\~/$HOME}"
+    fi
+
+    # Expand environment variables
+    # Handle both $VAR and ${VAR} syntax
+    path=$(eval echo "$path")
+
+    echo "$path"
+}
+
+# path_exists - Check if path exists (after resolution)
+# Usage: if path_exists "~/file"; then ...
+path_exists() {
+    local path
+    path=$(path_resolve "$1")
+    [ -e "$path" ]
+}
+
+# =============================================================================
+# Shell Detection and Version
+# =============================================================================
+
+# get_shell_version - Get bash version
+# Usage: VERSION=$(get_shell_version)
+get_shell_version() {
+    echo "${BASH_VERSION:-unknown}"
+}
+
+# check_bash_version - Check if bash version meets minimum requirement
+# Usage: check_bash_version "4.0"
+# Returns: 0 if meets requirement, 1 otherwise
+check_bash_version() {
+    local required="$1"
+    local current="${BASH_VERSINFO[0]}.${BASH_VERSINFO[1]}"
+
+    # Simple version comparison (assumes major.minor format)
+    local req_major req_minor cur_major cur_minor
+    req_major=$(echo "$required" | cut -d. -f1)
+    req_minor=$(echo "$required" | cut -d. -f2)
+    cur_major="${BASH_VERSINFO[0]}"
+    cur_minor="${BASH_VERSINFO[1]}"
+
+    if [ "$cur_major" -gt "$req_major" ]; then
+        return 0
+    elif [ "$cur_major" -eq "$req_major" ] && [ "$cur_minor" -ge "$req_minor" ]; then
+        return 0
+    else
+        return 1
+    fi
+}
+
+# =============================================================================
+# Utility Functions
+# =============================================================================
+
+# command_exists - Check if command is available
+# Usage: if command_exists "jq"; then ...
+command_exists() {
+    command -v "$1" &>/dev/null
+}
+
+# get_config_dir - Get platform-appropriate config directory
+# Usage: CONFIG_DIR=$(get_config_dir)
+get_config_dir() {
+    local platform
+    platform=$(detect_platform)
+
+    case "$platform" in
+        macos)
+            echo "${HOME}/Library/Application Support"
+            ;;
+        linux|windows)
+            echo "${XDG_CONFIG_HOME:-${HOME}/.config}"
+            ;;
+        *)
+            echo "${HOME}/.config"
+            ;;
+    esac
+}
+
+# ensure_dir - Ensure directory exists
+# Usage: ensure_dir "/path/to/dir"
+ensure_dir() {
+    local dir="$1"
+    if [ ! -d "$dir" ]; then
+        mkdir -p "$dir"
+    fi
+}
+
+# =============================================================================
+# Export Functions (for sourcing)
+# =============================================================================
+
+# When sourced, make functions available
+if [ "${BASH_SOURCE[0]}" != "${0}" ]; then
+    export -f detect_platform
+    export -f timeout_cmd
+    export -f wait_for_pid
+    export -f make_temp_file
+    export -f make_temp_dir
+    export -f json_get
+    export -f json_has_key
+    export -f path_resolve
+    export -f path_exists
+    export -f get_shell_version
+    export -f check_bash_version
+    export -f command_exists
+    export -f get_config_dir
+    export -f ensure_dir
+fi

package/package.json

@@ -0,0 +1,46 @@
+{
+  "name": "llm-cli-council",
+  "version": "1.0.0",
+  "description": "Get diverse AI perspectives on your code and plans via multiple LLM CLIs — orchestrates Claude, GitHub Copilot, Codex, Gemini, and Ollama as a council",
+  "bin": {
+    "llm-cli-council": "bin/install.js"
+  },
+  "files": [
+    "bin",
+    "skills",
+    "lib",
+    "prompts",
+    "rules",
+    "config",
+    ".claude-plugin"
+  ],
+  "keywords": [
+    "claude",
+    "claude-code",
+    "llm",
+    "code-review",
+    "copilot",
+    "codex",
+    "gemini",
+    "ollama",
+    "claude-plugin",
+    "ai-council"
+  ],
+  "author": "GuitaristForEver",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/GuitaristForEver/llm-cli-council.git"
+  },
+  "homepage": "https://github.com/GuitaristForEver/llm-cli-council#readme",
+  "bugs": {
+    "url": "https://github.com/GuitaristForEver/llm-cli-council/issues"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "scripts": {
+    "test": "bash tests/test-setup.sh",
+    "prepublishOnly": "npm test"
+  }
+}

package/prompts/chairman-synthesis.md

@@ -0,0 +1,153 @@
+# Chairman Synthesis Prompt
+
+Claude acts as Chairman of the council, synthesizing multiple provider reviews into unified guidance.
+
+---
+
+## Chairman Role
+
+As Chairman, you:
+1. **Synthesize** - Combine multiple reviews into coherent guidance
+2. **Resolve** - Make decisions when providers disagree
+3. **Prioritize** - Order recommendations by importance
+4. **Decide** - Provide final APPROVE/REQUEST CHANGES verdict
+
+---
+
+## Synthesis Prompt Template
+
+```
+TASK: As Chairman of the LLM Council, synthesize the following provider reviews into unified guidance.
+
+REVIEWS RECEIVED:
+{PROVIDER_REVIEWS}
+
+SYNTHESIS RULES:
+1. CONSENSUS: Points raised by 2+ providers go here
+2. CONCERNS: Points raised by at least one provider that merit attention
+3. DISSENT: Where providers disagree - YOU must resolve with reasoning
+4. Maximum 5 recommendations total, ordered by priority
+5. You MUST provide a final verdict
+
+ANTI-PARALYSIS RULES:
+- Do NOT present conflicting advice without resolution
+- Do NOT defer decisions to the user
+- Do NOT exceed 5 recommendations
+- Do NOT leave verdict ambiguous
+
+WEIGHTING:
+- For code-related plans: Weight Codex and Copilot higher
+- For architecture plans: Weight Claude higher
+- For general plans: Equal weighting
+
+OUTPUT FORMAT:
+COUNCIL REVIEW
+═══════════════════════════════════════════════════════
+
+CONSENSUS (All/Majority agree):
+• [Point that 2+ providers agree on]
+• [Another consensus point]
+
+CONCERNS (Raised by at least one):
+• [Concern] — Raised by: [Provider names]
+  Assessment: [Your assessment of validity/priority]
+
+DISSENTING VIEWS:
+• [Topic]: [Provider A] says X, [Provider B] says Y
+  Resolution: [Your decision with reasoning]
+
+RECOMMENDATIONS (max 5, prioritized):
+1. [Most important] [Quick/Short/Medium effort estimate]
+2. [Second priority] [Effort]
+3. [Third priority] [Effort]
+
+PROVIDER VERDICTS:
+  [Provider 1]: [VERDICT] ([CONFIDENCE])
+  [Provider 2]: [VERDICT] ([CONFIDENCE])
+
+FINAL VERDICT: [APPROVE / REQUEST CHANGES]
+Reasoning: [Clear explanation of why, referencing provider input]
+
+═══════════════════════════════════════════════════════
+```
+
+---
+
+## Variable Substitution
+
+| Variable | Source |
+|----------|--------|
+| `{PROVIDER_REVIEWS}` | Concatenated reviews from all providers, each prefixed with provider name |
+
+---
+
+## Review Formatting
+
+Format each provider review as:
+
+```
+--- REVIEW FROM: [PROVIDER NAME] ---
+[Full review content]
+--- END REVIEW ---
+```
+
+---
+
+## Resolution Guidelines
+
+### When Providers Disagree on Verdict
+
+1. **Majority rules** if 2+ providers agree
+2. **Tie-breaker**: Weight by task type (code → Codex, architecture → Claude)
+3. **All disagree**: Chairman decides based on strongest reasoning
+
+### When Recommendations Conflict
+
+1. Evaluate each recommendation on merit
+2. Keep recommendations that don't contradict
+3. For contradictions, pick one and explain why
+
+### Effort Estimates
+
+Standardize to:
+- **Quick**: < 1 hour
+- **Short**: 1-4 hours
+- **Medium**: 1-2 days
+- **Large**: 3+ days
+
+---
+
+## Output Validation
+
+Before presenting synthesis, verify:
+- [ ] Maximum 5 recommendations
+- [ ] All dissent has resolution
+- [ ] Final verdict is clear (not "probably" or "maybe")
+- [ ] Reasoning references specific provider input
+- [ ] No raw provider output passed through
+
+---
+
+## Error Cases
+
+### Only 1 Provider Responded
+```
+Note: Only [Provider] responded. This review lacks council diversity.
+Consider running with --mode=full for comprehensive feedback.
+
+[Present single review with disclaimer]
+```
+
+### All Providers Approve
+```
+CONSENSUS: All providers approve this plan.
+
+[Present combined recommendations anyway - unanimous approval doesn't mean perfect]
+```
+
+### All Providers Request Changes
+```
+STRONG CONSENSUS: All providers request changes.
+
+[Prioritize most critical issues across all reviews]
+```

package/prompts/code-review.md

@@ -0,0 +1,134 @@
+# Code Review Prompt Template
+
+This template is sent to each council provider for independent code review.
+
+---
+
+## Prompt Template
+
+```
+TASK: Review the following code changes for bugs, security issues, performance problems, and maintainability concerns.
+
+EXPECTED OUTCOME: Provide a structured code review with:
+- Assessment of code quality (1-10 scale)
+- Identified issues categorized by severity
+- Specific recommendations with file/line references
+- Final verdict: APPROVE, REQUEST CHANGES, or REJECT
+
+CONTEXT:
+- This is a code review, not implementation
+- Focus on issues that matter, not style nitpicks
+- Prioritize: Correctness → Security → Performance → Maintainability
+
+CODE CHANGES:
+---
+{CODE_CONTENT}
+---
+
+FILES AFFECTED:
+{FILE_LIST}
+
+CONSTRAINTS:
+- You are one voice in a council of reviewers
+- Keep feedback actionable and specific
+- Reference file:line when possible
+
+MUST DO:
+1. Rate code quality on 1-10 scale with justification
+2. List issues by severity: CRITICAL | HIGH | MEDIUM | LOW
+3. For each issue: file, line (if known), description, suggested fix
+4. Provide 3-5 actionable recommendations
+5. Give clear verdict: APPROVE | REQUEST CHANGES | REJECT
+
+MUST NOT DO:
+- Nitpick formatting (let formatters handle this)
+- Flag theoretical concerns unlikely to occur
+- Suggest complete rewrites for minor issues
+- Be overly verbose
+
+OUTPUT FORMAT:
+RATING: [1-10] - [one-line justification]
+
+ISSUES:
+CRITICAL:
+• [file:line] [Description] → [Suggested fix]
+
+HIGH:
+• [file:line] [Description] → [Suggested fix]
+
+MEDIUM:
+• [file:line] [Description] → [Suggested fix]
+
+LOW:
+• [file:line] [Description] → [Suggested fix]
+
+RECOMMENDATIONS:
+1. [Specific recommendation]
+2. [Specific recommendation]
+3. [Specific recommendation]
+
+VERDICT: [APPROVE / REQUEST CHANGES / REJECT]
+CONFIDENCE: [HIGH / MEDIUM / LOW]
+REASONING: [1-2 sentences explaining verdict]
+```
+
+---
+
+## Variable Substitution
+
+| Variable | Source |
+|----------|--------|
+| `{CODE_CONTENT}` | Git diff, file contents, or pasted code |
+| `{FILE_LIST}` | List of files being reviewed |
+
+---
+
+## Provider-Specific Adjustments
+
+### Claude
+No adjustments - template works as-is.
+
+### Codex
+Add prefix: "You are an expert code reviewer. Focus on bugs and security issues."
+
+### Copilot
+Add prefix: "Review this code from a GitHub PR perspective. Be specific about issues."
+
+### Gemini
+Add prefix: "Provide comprehensive code review covering all quality aspects."
+
+### Ollama
+Simplify for smaller models - focus on critical issues only.
+
+---
+
+## Response Parsing
+
+Expected response sections to parse:
+1. `RATING:` line with number and justification
+2. `ISSUES:` with severity categories
+3. `RECOMMENDATIONS:` numbered list
+4. `VERDICT:` APPROVE, REQUEST CHANGES, or REJECT
+5. `CONFIDENCE:` HIGH, MEDIUM, or LOW
+6. `REASONING:` explanation
+
+---
+
+## Issue Severity Definitions
+
+| Severity | Definition | Example |
+|----------|------------|---------|
+| CRITICAL | Security vulnerability, data loss risk, crash | SQL injection, null pointer |
+| HIGH | Bug that affects functionality | Wrong calculation, broken feature |
+| MEDIUM | Code smell, maintainability issue | Complex function, poor naming |
+| LOW | Minor improvement opportunity | Documentation, minor refactor |
+
+---
+
+## Verdict Definitions
+
+| Verdict | When to Use |
+|---------|-------------|
+| APPROVE | No critical/high issues, code is ready to merge |
+| REQUEST CHANGES | Has high issues or multiple medium issues needing fix |
+| REJECT | Critical issues or fundamentally flawed approach |