@yeongjaeyou/claude-code-config 0.15.0 → 0.17.0

package/.claude/commands/council.md

@@ -23,11 +23,53 @@ Inspired by Andrej Karpathy's LLM Council: query multiple AI models with the sam
 3. **Quick mode**: `/council --quick What's the best approach?`
 
 **Flags:**
-- `--quick`: Quick mode - reduced reasoning depth, faster convergence
+- `--quick`: Quick mode (see below)
 
 **Default behavior (no flags):**
-- Maximum reasoning depth (Codex: xhigh + gpt-5.1-codex-max)
+- Maximum reasoning depth (Codex: reasoningEffort=xhigh, model=gpt-5.1-codex-max)
 - Full multi-round deliberation (up to 3 rounds)
+- YAML schema enforced
+
+**Quick mode (`--quick`):**
+- All 4 models queried (Opus, Sonnet, Codex, Gemini)
+- Single round only (Round 1 -> direct Synthesis, no Round 1.5 analysis)
+- YAML schema not enforced (free-form responses accepted)
+- Codex: reasoningEffort=high (instead of xhigh)
+
+---
+
+## Pre-flight Check
+
+Before querying models, verify environment parity:
+
+**1. CLI Installation:**
+```bash
+command -v claude && echo "Claude Code: OK" || echo "Claude Code: Missing"
+command -v codex && echo "Codex CLI: OK" || echo "Codex CLI: Missing"
+command -v gemini && echo "Gemini CLI: OK" || echo "Gemini CLI: Missing"
+```
+
+**2. Guidelines Files:**
+```bash
+[ -f ./CLAUDE.md ] && echo "CLAUDE.md: OK" || echo "CLAUDE.md: Missing"
+[ -f ./AGENTS.md ] && echo "AGENTS.md: OK" || echo "AGENTS.md: Missing"
+[ -f ./GEMINI.md ] && echo "GEMINI.md: OK" || echo "GEMINI.md: Missing"
+```
+
+**3. MCP Configuration:**
+| CLI | Config Location | Check Command |
+|-----|-----------------|---------------|
+| Claude Code | `.mcp.json`, `~/.claude.json` | `claude mcp list` |
+| Codex CLI | `~/.codex/config.toml` | `codex mcp --help` |
+| Gemini CLI | `~/.gemini/settings.json`, `.gemini/settings.json` | `gemini mcp list` |
+
+**Warning conditions (proceed with caution):**
+- Guidelines file missing: model runs without project context
+- MCP not configured: model has limited tool access
+- CLI not installed: model excluded from council
+
+**If warnings detected:**
+Use AskUserQuestion to confirm whether to proceed or fix issues first.
 
 ---
 
@@ -41,15 +83,14 @@ council_member:
   response:
     summary: "1-2 sentence core answer"
     detailed_answer: "full response content"
-    confidence: 0.0-1.0
     key_points:
       - point: "key insight"
         evidence: "file:line or reasoning"
-    code_references:
+    code_references:  # optional
       - file: "/absolute/path/to/file.py"
         lines: "42-58"
         context: "why this is relevant"
-    caveats:
+    caveats:  # optional
       - "potential limitation or edge case"
   # Round 2+ additional fields
   gaps:
@@ -72,7 +113,6 @@ Before querying models, collect relevant context:
 ```
 - git status / git diff (current changes)
 - Directory structure (tree -L 2)
-- Files mentioned in conversation (Read/Edit history)
 
 Model-specific guidelines (project root):
 - ./CLAUDE.md (Claude Opus/Sonnet)
@@ -80,6 +120,38 @@ Model-specific guidelines (project root):
 - ./gemini.md (Gemini)
 ```
 
+**Conditional Code Exploration:**
+
+When relevant files are unclear from the question, spawn Explore agents to discover them:
+
+```
+Trigger conditions:
+- Question mentions code/architecture/structure without specific files
+- Question asks about "this", "the code", "current implementation" ambiguously
+- UI/UX questions that need component/style file identification
+
+Skip exploration when:
+- User provides specific file paths or permalinks
+- Question is conceptual (no code context needed)
+- Files are obvious from recent git diff
+```
+
+```
+Task(subagent_type="Explore", run_in_background: true):
+  prompt: |
+    Find files related to: [USER_QUESTION]
+
+    Return results in this format:
+    - /absolute/path/file.ext:LINE-LINE (brief context)
+
+    Focus on:
+    - Direct implementation files
+    - Related tests
+    - Configuration if relevant
+```
+
+After exploration, use discovered paths in the File Path Inclusion format below.
+
 **File Path Inclusion (MANDATORY format):**
 ```
 Relevant files for this question:
@@ -95,7 +167,7 @@ Use your file access tools to READ these files directly.
 |-------|-------------------|
 | Claude Opus/Sonnet | Read tool (images supported) |
 | Codex | sandbox read-only file access |
-| Gemini | Include file content in prompt, or instruct to read |
+| Gemini | MCP tools or Bash file read (MCP supported since 2025) |
 
 **Sensitive Data Filtering (exclude from prompts):**
 ```
@@ -114,6 +186,41 @@ Directories: node_modules/, __pycache__/, .git/
 
 ---
 
+## Progress Tracking
+
+Use TodoWrite to show progress at each stage:
+
+**Round 1 start:**
+```yaml
+todos:
+  - content: "[Council] Query Opus"
+    status: "in_progress"
+    activeForm: "Querying Opus"
+  - content: "[Council] Query Sonnet"
+    status: "in_progress"
+    activeForm: "Querying Sonnet"
+  - content: "[Council] Query Codex"
+    status: "in_progress"
+    activeForm: "Querying Codex"
+  - content: "[Council] Query Gemini"
+    status: "in_progress"
+    activeForm: "Querying Gemini"
+  - content: "[Council] Analyze responses"
+    status: "pending"
+    activeForm: "Analyzing responses"
+  - content: "[Council] Synthesize"
+    status: "pending"
+    activeForm: "Synthesizing"
+```
+
+**Update rules:**
+- Model response received -> mark that model's todo as "completed"
+- All models done -> "[Council] Analyze responses" to "in_progress"
+- Round 2 needed -> add re-query todos for specific models
+- Analysis done -> "[Council] Synthesize" to "in_progress"
+
+---
+
 ## Execution
 
 ### Round 1: Collect Initial Responses
@@ -160,7 +267,7 @@ Task(subagent_type="general-purpose", run_in_background: true):
     You are participating in an LLM Council deliberation as Codex.
 
     ## Tool Usage
-    Use mcp__codex__codex tool with:
+    Use mcp__codex-cli__codex tool with:
     - sandbox: "read-only"
     - workingDirectory: "{PROJECT_ROOT}"
     - reasoningEffort: "xhigh"  (or "high" with --quick)
@@ -196,6 +303,8 @@ Task(subagent_type="general-purpose", run_in_background: true):
     [GEMINI_PROMPT_WITH_CONTEXT]
     EOF
     ```
+    Note: Gemini CLI supports MCP (since 2025). If MCP is configured,
+    Gemini can access project files directly via MCP tools.
 
     ## Guidelines
     Read and follow ./gemini.md project guidelines.
@@ -204,8 +313,8 @@ Task(subagent_type="general-purpose", run_in_background: true):
     ## Question
     [USER_QUESTION]
 
-    ## Context Files (include content since Gemini has limited file access)
-    [FILE_CONTENTS_WITH_LINE_NUMBERS]
+    ## Context Files (READ directly using exact paths)
+    [FILE_LIST_WITH_LINE_NUMBERS]
 
     ## Instructions
     Parse Gemini's response and return structured YAML following the schema.
@@ -232,15 +341,15 @@ Skipping Round 1.5 defeats the purpose of multi-round deliberation.
 
 **1. Anonymize Responses:**
 ```
-1. Shuffle response order randomly
-2. Assign labels: Response A, B, C, D
-3. Create internal mapping:
+1. Assign labels in response arrival order: Response A, B, C, D
+2. Create internal mapping:
    label_to_model = {
-     "Response A": "gemini",
-     "Response B": "opus",
-     "Response C": "sonnet",
-     "Response D": "codex"
+     "Response A": "[first arrived]",
+     "Response B": "[second arrived]",
+     "Response C": "[third arrived]",
+     "Response D": "[fourth arrived]"
    }
+3. Present responses by label only (hide model names until synthesis)
 ```
 
 **2. Gap Analysis:**
@@ -271,16 +380,17 @@ conflicts_detected:
 **4. Convergence Check (REQUIRED before synthesis):**
 ```yaml
 convergence_status:
-  confidence_average: 0.815
-  new_information_ratio: 0.15
+  agreement_count: 3  # models with same core conclusion
   gaps_remaining: 2
   conflicts_remaining: 1
   decision: "proceed_to_round_2" | "terminate_and_synthesize"
 ```
 
 **Decision logic:**
-- If `gaps_remaining > 0` AND `confidence_average < 0.9` → `proceed_to_round_2`
+- If `agreement_count >= 3` → `terminate_and_synthesize` (strong consensus)
+- If `gaps_remaining == 0` AND `conflicts_remaining == 0` → `terminate_and_synthesize`
 - If `conflicts_remaining > 0` AND round < 3 → `proceed_to_round_2`
+- If `gaps_remaining > 0` AND round < 3 → `proceed_to_round_2`
 - Otherwise → `terminate_and_synthesize`
 
 ### Round 2: Targeted Re-queries (Conditional)
@@ -292,11 +402,11 @@ If convergence criteria not met, re-query only models with gaps/conflicts:
 ## Previous Round Summary
 Round 1 produced the following positions:
 
-### Response A (Confidence: 0.92)
+### Response A
 - Position: [summary]
 - Key points: [list]
 
-### Response B (Confidence: 0.85)
+### Response B
 - Position: [summary]
 - Key points: [list]
 
@@ -317,7 +427,6 @@ Please address specifically:
 2. [specific gap or conflict to resolve]
 
 Provide evidence and reasoning for your position.
-Update your confidence score based on new information.
 
 ## Output (YAML format required)
 [COUNCIL_MEMBER_SCHEMA with gaps/conflicts fields]
@@ -362,10 +471,9 @@ After convergence or max rounds:
 ### Soft Limits (Convergence - any triggers termination)
 | Condition | Threshold |
 |-----------|-----------|
-| Average confidence | > 0.9 |
-| New information ratio | < 10% |
+| Strong consensus | 3+ models agree on core conclusion |
 | All gaps resolved | 0 remaining |
-| Strong consensus | 3+ models agree |
+| All conflicts resolved | 0 remaining |
 | Conflicts irreconcilable | Cannot be resolved with more queries |
 
 ---
@@ -387,29 +495,29 @@ After convergence or max rounds:
 
 ### Individual Responses (Anonymized)
 
-#### Response A (Confidence: 0.92)
+#### Response A
 [Content]
 
 **Key Points:**
 - [point 1] (evidence: file:line)
 - [point 2] (evidence: file:line)
 
-#### Response B (Confidence: 0.85)
+#### Response B
 [Content]
 
-#### Response C (Confidence: 0.78)
+#### Response C
 [Content]
 
-#### Response D (Confidence: 0.71)
+#### Response D
 [Content]
 
 ### Model Reveal
-| Label | Model | Final Confidence |
-|-------|-------|-----------------|
-| Response A | codex | 0.92 |
-| Response B | opus | 0.85 |
-| Response C | sonnet | 0.78 |
-| Response D | gemini | 0.71 |
+| Label | Model |
+|-------|-------|
+| Response A | codex |
+| Response B | opus |
+| Response C | sonnet |
+| Response D | gemini |
 
 ### Coordinator Analysis
 

package/.claude/commands/gh/auto-review-loop.md

@@ -0,0 +1,201 @@
+---
+description: Automatically fix CodeRabbit PR review comments until resolved
+---
+
+# Auto PR Review Loop
+
+Automatically fix and push until CodeRabbit review comments reach zero.
+
+## Arguments
+
+`$ARGUMENTS` parsing:
+- **No arguments**: Use current branch's PR
+- **PR number**: `/gh:auto-review-loop 123` - Specify PR
+
+## Safety Limits
+
+- **MAX_ITERATIONS**: 10 (prevent infinite loops)
+- **POLL_INTERVAL**: 30 seconds (API rate limit consideration)
+- **POLL_TIMEOUT**: 300 seconds (max wait time for review)
+
+## Workflow
+
+### 1. Get PR Info
+
+```bash
+# Get PR number and repo info
+PR_NUMBER=${ARGUMENTS:-$(gh pr view --json number -q .number 2>/dev/null)}
+REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
+OWNER=$(echo "$REPO" | cut -d'/' -f1)
+REPO_NAME=$(echo "$REPO" | cut -d'/' -f2)
+
+echo "Target PR: #${PR_NUMBER} in ${REPO}"
+```
+
+### 2. Start Iteration Loop
+
+```
+MAX_ITERATIONS=10
+ITERATION=0
+
+while [ $ITERATION -lt $MAX_ITERATIONS ]; do
+  ITERATION=$((ITERATION + 1))
+  echo "=== Iteration $ITERATION/$MAX_ITERATIONS ==="
+```
+
+### 3. Poll for Unresolved CodeRabbit Comments
+
+Use GraphQL API with file-based query (inline `$` causes bash variable expansion issues):
+
+```bash
+# Timeout settings: first iteration waits longer for initial review
+POLL_TIMEOUT_INITIAL=300   # First iteration: 5 minutes
+POLL_TIMEOUT_SUBSEQUENT=120  # Subsequent iterations: 2 minutes (wait for new review)
+POLL_INTERVAL=30
+MIN_WAIT_BEFORE_EXIT=60  # Minimum wait before declaring "all resolved"
+
+if [ $ITERATION -eq 1 ]; then
+  CURRENT_TIMEOUT=$POLL_TIMEOUT_INITIAL
+else
+  CURRENT_TIMEOUT=$POLL_TIMEOUT_SUBSEQUENT
+fi
+
+ELAPSED=0
+
+# Create GraphQL query file (avoids $ variable expansion in bash)
+cat > /tmp/gh_review_query.graphql << 'GRAPHQL'
+query($owner: String!, $repo: String!, $pr: Int!) {
+  repository(owner: $owner, name: $repo) {
+    pullRequest(number: $pr) {
+      reviewThreads(first: 100) {
+        nodes {
+          isResolved
+          path
+          line
+          comments(first: 1) {
+            nodes {
+              author { login }
+              body
+            }
+          }
+        }
+      }
+    }
+  }
+}
+GRAPHQL
+
+echo "Waiting for CodeRabbit review... (timeout: ${CURRENT_TIMEOUT}s)"
+while [ $ELAPSED -lt $CURRENT_TIMEOUT ]; do
+  # Query unresolved review threads from CodeRabbit
+  # Filter: unresolved + coderabbit + NOT nitpick (actionable only)
+  UNRESOLVED=$(gh api graphql \
+    -F query=@/tmp/gh_review_query.graphql \
+    -f owner="$OWNER" -f repo="$REPO_NAME" -F pr="$PR_NUMBER" \
+    --jq '[.data.repository.pullRequest.reviewThreads.nodes[] |
+      select(.isResolved == false) |
+      select(.comments.nodes[0].author.login | contains("coderabbit")) |
+      select(.comments.nodes[0].body | (contains("<!-- nitpick -->") or contains("[nitpick]")) | not)] | length')
+
+  if [ "$UNRESOLVED" -gt 0 ]; then
+    echo "Found $UNRESOLVED unresolved CodeRabbit comments"
+    break
+  fi
+
+  # For subsequent iterations: require minimum wait before exit
+  if [ $ITERATION -gt 1 ] && [ $ELAPSED -ge $MIN_WAIT_BEFORE_EXIT ]; then
+    echo "No new comments after ${MIN_WAIT_BEFORE_EXIT}s wait. All resolved!"
+    exit 0
+  fi
+
+  sleep $POLL_INTERVAL
+  ELAPSED=$((ELAPSED + POLL_INTERVAL))
+  echo "Still waiting... ($ELAPSED/$CURRENT_TIMEOUT seconds)"
+done
+
+# Handle timeout
+if [ "$UNRESOLVED" -eq 0 ]; then
+  if [ $ITERATION -eq 1 ]; then
+    echo "No CodeRabbit review received within timeout. Exiting."
+    exit 0
+  else
+    echo "All CodeRabbit comments resolved!"
+    exit 0
+  fi
+fi
+```
+
+### 4. Extract Unresolved Comments
+
+```bash
+# Extract actionable comments only (exclude nitpick)
+REVIEW_CONTENT=$(gh api graphql \
+  -F query=@/tmp/gh_review_query.graphql \
+  -f owner="$OWNER" -f repo="$REPO_NAME" -F pr="$PR_NUMBER" \
+  --jq '.data.repository.pullRequest.reviewThreads.nodes[] |
+    select(.isResolved == false) |
+    select(.comments.nodes[0].author.login | contains("coderabbit")) |
+    select(.comments.nodes[0].body | (contains("<!-- nitpick -->") or contains("[nitpick]")) | not) |
+    "File: \(.path)\nLine: \(.line)\n\nComment:\n\(.comments.nodes[0].body)\n\n---"')
+
+echo "=== Unresolved CodeRabbit Comments ==="
+echo "$REVIEW_CONTENT"
+```
+
+### 5. Apply Fixes
+
+Read `.claude/commands/code-review.md` and process each comment following its Auto-fix vs Checklist criteria.
+
+### 6. Commit & Push
+
+```bash
+# Check for changes
+if [ -n "$(git status --porcelain)" ]; then
+  git add -u
+  git commit -m "fix: apply CodeRabbit review (iteration $ITERATION)"
+  git push
+  echo "Changes pushed. Waiting for next review..."
+  sleep 60  # Wait for new review
+else
+  echo "No changes to commit"
+  break
+fi
+```
+
+### 7. Loop Termination
+
+```
+done  # end while loop
+
+if [ $ITERATION -ge $MAX_ITERATIONS ]; then
+  echo "Max iterations reached. Manual review may be required."
+  exit 1
+fi
+```
+
+## Output Format
+
+Each iteration outputs:
+```
+=== Iteration N/10 ===
+- Unresolved comments: X
+- Auto-fixed: Y
+- Requires confirmation: Z
+- Pushed commit: abc1234
+```
+
+## Error Handling
+
+| Error | Response |
+|-------|----------|
+| PR not found | Exit with error message |
+| API rate limit | Increase poll interval, retry |
+| No CodeRabbit review | Exit after timeout |
+| Git push failed | Report error, stop iteration |
+
+## Guidelines
+
+- Follow `@CLAUDE.md` project conventions
+- Use `AskUserQuestion` for architecture/logic changes
+- Never auto-fix business logic without confirmation
+- Commit only issue-relevant files (no `git add -A`)

package/.claude/commands/gh/create-issue-label.md

@@ -1,3 +1,7 @@
+---
+description: Create Issue Labels
+---
+
 ## Create Issue Labels
 
 Analyze project structure and create appropriate GitHub issue labels. Follow project guidelines in `@CLAUDE.md`.

package/.claude/commands/gh/decompose-issue.md

@@ -1,3 +1,7 @@
+---
+description: Decompose Work
+---
+
 ## Decompose Work
 
 Break down large work items into manageable, independent issues. Follow project guidelines in `@CLAUDE.md`.
@@ -65,8 +69,10 @@ Examples (vary by project, for reference only):
 - `path/filename` - Change description
 
 **Completion criteria**:
-- [ ] Feature implementation complete
-- [ ] Added to demo page (for UI components)
+- [ ] Implementation complete (all tasks checked)
+- [ ] Execution verified (no runtime errors)
+- [ ] Tests pass (if applicable)
+- [ ] Added to demo page (for UI components, if applicable)
 
 **Dependencies**:
 - [ ] None or prerequisite issue #number
@@ -167,3 +173,19 @@ MCP: none
 Skills: ...
 MCP: ...
 ```
+
+---
+
+## Verification Guidelines
+
+이슈 작업 완료 시 반드시 실행 검증 수행:
+
+| 작업 유형 | 검증 방법 |
+|-----------|-----------|
+| Python 코드 | `python -m py_compile file.py` + 실제 실행 |
+| TypeScript/JS | `tsc --noEmit` 또는 빌드 |
+| API/서버 | 엔드포인트 호출 테스트 |
+| CLI 도구 | 기본 명령어 실행 |
+| 설정 파일 | 관련 도구로 로드 확인 |
+
+**파일만 생성하고 실행 검증 없이 완료 처리 금지**

package/.claude/commands/gh/post-merge.md

@@ -54,16 +54,37 @@ Perform branch cleanup and CLAUDE.md updates after a PR has been merged. Follow
 6. **Analyze and Update Configuration Files**
    - Check which configuration files exist:
      - `CLAUDE.md` - Claude Code specific instructions
-     - `AGENTS.md` - Cross-tool AI coding agent instructions (Codex, Cursor, Gemini, etc.)
+     - `AGENTS.md` - Cross-tool AI coding agent instructions
      - `GEMINI.md` - Google Gemini CLI specific instructions
-   - For each existing file, analyze:
-     - Find temporary instructions related to resolved issue (e.g., mentions of `#<issue_number>`, `issue-<number>`)
-     - Identify outdated or inaccurate information
-     - Identify redundant or unnecessary content
-   - Prepare update proposal for each file:
-     - **To remove**: Temporary notes/instructions related to resolved issue
-     - **To add**: New patterns/conventions discovered during issue resolution
-     - **To modify**: Outdated or inaccurate information
+     - `.claude/rules/*.md` - Modular rule files
+
+   - **Placement Rules** (applies to all config files):
+
+     | Content Type | Placement |
+     |--------------|-----------|
+     | Project-wide constraints | Golden Rules > Immutable |
+     | Project-wide recommendations | Golden Rules > Do's |
+     | Project-wide prohibitions | Golden Rules > Don'ts |
+     | Module-specific rules | Delegate to `.claude/rules/[module].md` |
+     | New commands | Commands section |
+     | New module references | Modular Rules section |
+
+   - **Content Removal**:
+     - Temporary instructions (e.g., `TODO: remove after #N`)
+     - Resolved known issues
+     - Workaround descriptions for fixed bugs
+
+   - **Content Addition**:
+     - Module-specific rule -> propose `.claude/rules/[module].md` creation/update
+     - Project-wide rule -> add to appropriate Golden Rules subsection
+     - New module documented -> add `See @.claude/rules/[module].md` reference
+
+   - **Modular Rule Files** (.claude/rules/*.md):
+     - Check if relevant module file exists
+     - Propose path-specific rules with frontmatter: `paths: src/[module]/**/*.py`
+     - Follow structure: Role, Key Components, Do's, Don'ts
+     - **Always confirm with user before creating new rule files**
+
    - Present proposal to user for confirmation before applying
 
 7. **Commit Changes (Optional)**
@@ -75,7 +96,28 @@ Perform branch cleanup and CLAUDE.md updates after a PR has been merged. Follow
 
 ## Configuration File Update Guide
 
-The following guidelines apply to CLAUDE.md, AGENTS.md, and GEMINI.md:
+The following guidelines apply to CLAUDE.md, AGENTS.md, GEMINI.md, and `.claude/rules/*.md`:
+
+### Expected File Structure
+
+**Root Config (CLAUDE.md, AGENTS.md, GEMINI.md)**:
+1. Project Context - Business goal + tech stack (1-2 sentences)
+2. Commands - Package manager and run commands
+3. Golden Rules - Immutable / Do's / Don'ts
+4. Modular Rules - `See @.claude/rules/[module].md` references
+5. Project-Specific - Data locations, tracking, etc.
+
+**Modular Rules (.claude/rules/*.md)**:
+```markdown
+---
+paths: src/[module]/**/*.py  # Optional: conditional loading
+---
+# [Module] Rules
+Role description (1-2 lines)
+## Key Components
+## Do's
+## Don'ts
+```
 
 ### Examples of Content to Remove
 - Temporary notes like `TODO: remove after #123 is resolved`