@lvlup-sw/exarchos 2.7.1 → 2.8.0

package/skills/opencode/synthesis/references/github-native-stacking.md

@@ -8,15 +8,15 @@ PR stacking creates a chain of dependent pull requests that merge bottom-up into
 
 ## 1. PR Chain Creation
 
-Create PRs that chain together by setting each PR's `--base` to the previous branch:
+Create PRs that chain together by setting each PR's base to the previous branch:
 
-```bash
-# First PR in chain targets main
-gh pr create --base main --head feat/step-1 --title "feat: step 1" --body "..."
+```typescript
+// First PR in chain targets main
+exarchos_orchestrate({ action: "create_pr", base: "main", head: "feat/step-1", title: "feat: step 1", body: "..." })
 
-# Subsequent PRs target the previous PR's branch
-gh pr create --base feat/step-1 --head feat/step-2 --title "feat: step 2" --body "..."
-gh pr create --base feat/step-2 --head feat/step-3 --title "feat: step 3" --body "..."
+// Subsequent PRs target the previous PR's branch
+exarchos_orchestrate({ action: "create_pr", base: "feat/step-1", head: "feat/step-2", title: "feat: step 2", body: "..." })
+exarchos_orchestrate({ action: "create_pr", base: "feat/step-2", head: "feat/step-3", title: "feat: step 3", body: "..." })
 ```
 
 The resulting chain looks like:
@@ -72,15 +72,14 @@ After rebasing a mid-stack branch, all downstream branches in the stack must als
 
 View the current PR chain and its state:
 
-```bash
-# List all open PRs with base/head branch relationships
-gh pr list --json number,baseRefName,headRefName,title,state \
-  --jq '.[] | "\(.number): \(.baseRefName) <- \(.headRefName) [\(.state)]"'
-
-# Example output:
-# 101: main <- feat/step-1 [OPEN]
-# 102: feat/step-1 <- feat/step-2 [OPEN]
-# 103: feat/step-2 <- feat/step-3 [OPEN]
+```typescript
+// List all open PRs with base/head branch relationships
+exarchos_orchestrate({ action: "list_prs", state: "open" })
+
+// Example output shows PR numbers, base/head branches, titles, and state:
+// 101: main <- feat/step-1 [OPEN]
+// 102: feat/step-1 <- feat/step-2 [OPEN]
+// 103: feat/step-2 <- feat/step-3 [OPEN]
 ```
 
 To validate stack integrity, use the `validate_pr_stack` action via orchestrate:
@@ -97,32 +96,29 @@ exarchos_orchestrate({
 GitHub's native merge queue ensures PRs pass CI before merging:
 
 - **Enable:** Repository Settings > Rules > Branch protection > Require merge queue
-- **Auto-merge:** `gh pr merge --auto --squash` enables auto-merge once checks pass
+- **Auto-merge:** `exarchos_orchestrate({ action: "merge_pr", prId: "<number>", strategy: "squash" })` enables auto-merge once checks pass
 - **For stacks:** Enable auto-merge on each PR, then merge bottom-up
 
-```bash
-# Enable auto-merge on all PRs in the stack
-gh pr merge 101 --auto --squash
-gh pr merge 102 --auto --squash
-gh pr merge 103 --auto --squash
-
-# Merge the first PR to start the cascade
-gh pr merge 101 --squash
+```typescript
+// Enable auto-merge on all PRs in the stack
+exarchos_orchestrate({ action: "merge_pr", prId: "101", strategy: "squash" })
+exarchos_orchestrate({ action: "merge_pr", prId: "102", strategy: "squash" })
+exarchos_orchestrate({ action: "merge_pr", prId: "103", strategy: "squash" })
 ```
 
 After PR 101 merges and its branch is deleted, GitHub retargets PR 102 to `main`. If auto-merge is enabled on PR 102, it merges automatically once CI passes.
 
-## 7. Graphite to GitHub-Native Equivalents
+## 7. Graphite to Exarchos MCP Equivalents
 
-| Graphite Command | GitHub-Native Equivalent |
+| Graphite Command | Exarchos MCP Equivalent |
 |---|---|
 | `gt create <branch> -m "feat: ..."` | `git checkout -b <branch> && git commit -m "feat: ..." && git push -u origin <branch>` |
-| `gt submit --no-interactive --publish --stack` | `gh pr create --base <base> --title "..." --body "..."` (per PR) |
-| `gt log` | `gh pr list --json number,baseRefName,headRefName` |
+| `gt submit --no-interactive --publish --stack` | `exarchos_orchestrate({ action: "create_pr", base: "<base>", title: "...", body: "..." })` (per PR) |
+| `gt log` | `exarchos_orchestrate({ action: "list_prs", state: "open" })` |
 | `gt modify -m "..."` | `git commit --amend -m "..." && git push --force-with-lease` |
 | `gt sync` | `git fetch --prune && git rebase origin/main` |
 | `gt restack` | `git rebase origin/<base-branch>` per branch in stack |
-| `mcp__graphite__run_gt_cmd` | `gh` CLI directly via Bash tool |
+| `mcp__graphite__run_gt_cmd` | `exarchos_orchestrate` VCS actions |
 
 ## 8. Error Handling
 

package/skills/opencode/synthesis/references/merge-ordering.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-GitHub-native stacked PRs merge bottom-up: the base branch merges first, then each dependent branch in sequence. This ordering is enforced by creating PRs with correct base branches and enabling auto-merge (`gh pr merge --auto --squash`).
+GitHub-native stacked PRs merge bottom-up: the base branch merges first, then each dependent branch in sequence. This ordering is enforced by creating PRs with correct base branches and enabling auto-merge via `exarchos_orchestrate({ action: "merge_pr", prId: "<number>", strategy: "squash" })`.
 
 ## Stack Ordering Rules
 

package/skills/opencode/synthesis/references/synthesis-steps.md

@@ -74,7 +74,7 @@ The script queries GitHub's PR reviews API for each PR, filters for CodeRabbit r
 **On `passed: true`:** All PRs are APPROVED or have no CodeRabbit review -- proceed to Step 5.
 **On `passed: false`:** At least one PR has CHANGES_REQUESTED or PENDING. The output identifies which PRs need attention. Route to fix cycle:
 ```typescript
-Skill({ skill: "exarchos:delegate", args: "--pr-fixes [PR_URL]" })
+Skill({ skill: "exarchos:shepherd", args: "[PR_URL]" })
 ```
 After fixes are applied, return to Step 4 to re-check.
 
@@ -121,13 +121,13 @@ mcp__plugin_exarchos_exarchos__exarchos_orchestrate({
 
 Create PRs for each branch in the stack (bottom-up) and enable auto-merge:
 
-```bash
-# For each branch in the stack (bottom-up):
-gh pr create --base <parent-branch> --head <branch> --title "<type>: <what>" --body "<pr-body>"
-gh pr merge <number> --auto --squash
+```typescript
+// For each branch in the stack (bottom-up):
+exarchos_orchestrate({ action: "create_pr", base: "<parent-branch>", head: "<branch>", title: "<type>: <what>", body: "<pr-body>" })
+exarchos_orchestrate({ action: "merge_pr", prId: "<number>", strategy: "squash" })
 ```
 
-After creation, use `gh pr list --json number,url,headRefName` to get the PR URLs for each stack entry.
+After creation, use `exarchos_orchestrate({ action: "list_prs", state: "open" })` to get the PR URLs for each stack entry.
 
 ## Step 7: Cleanup After Merge
 

package/skills/opencode/synthesis/references/troubleshooting.md

@@ -21,7 +21,7 @@ If tests fail during synthesis (they passed in review):
 ### Merge Queue Rejection
 
 If the merge queue rejects a PR:
-1. Check CI status via `gh pr checks <number>` (or GitHub MCP `pull_request_read` with method `get_status` if available)
+1. Check CI status via `exarchos_orchestrate({ action: "check_ci", prId: "<number>" })`
 2. Fix failing checks
 3. Push fixes and re-enqueue
 
@@ -29,20 +29,13 @@ If the merge queue rejects a PR:
 
 If the user receives PR review comments:
 
-1. Offer to address feedback:
+1. Route to the shepherd skill:
    ```typescript
-   Skill({ skill: "exarchos:delegate", args: "--pr-fixes [PR_URL]" })
+   Skill({ skill: "exarchos:shepherd", args: "[PR_URL]" })
    ```
 
-2. Delegate reads PR comments via gh CLI:
-   ```bash
-   gh pr view <number> --json reviews,comments
-   ```
-   > Or use GitHub MCP `pull_request_read` if available.
-
-3. Creates fix tasks from review comments
-4. After fixes, amend the commit with `git commit --amend -m "fix: <description>"` and push with `git push --force-with-lease`
-5. Return to merge confirmation
+2. Shepherd reads PR comments, assesses CI, and applies fixes directly
+3. After fixes, return to merge confirmation
 
 ## Final Report Template
 
@@ -50,7 +43,7 @@ If the user receives PR review comments:
 ## Synthesis Complete
 
 ### Pull Requests
-[PR URLs from gh pr list]
+[PR URLs from list_prs action]
 
 ### Stack Branches
 - task/001-types
@@ -88,11 +81,11 @@ If workflow state doesn't match git reality:
 3. Update state via `mcp__plugin_exarchos_exarchos__exarchos_workflow` with `action: "set"` to match git truth
 
 ## PR Creation Failed
-If `gh pr create` fails:
+If `create_pr` fails:
 1. Check the error output for specific guidance
-2. Run `gh pr list --json number,baseRefName,headRefName` to verify the branch state
+2. Run `exarchos_orchestrate({ action: "list_prs", state: "open" })` to verify the branch state
 3. If rebase conflict: run `git rebase origin/<base>` to resolve
-4. If authentication issue: check GitHub token permissions
+4. If authentication issue: check VCS provider token permissions
 
 ## Stack Rebase Conflict
 If `git rebase` encounters conflicts:
@@ -104,8 +97,8 @@ If `git rebase` encounters conflicts:
 
 When Exarchos MCP tools are available:
 
-1. **After stack submission:** Call `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` with event type `stack.enqueued` including PR numbers from `gh pr list --json number`
-2. **Monitor merge status:** Use `gh pr list --json number,state,mergedAt` to check stack/PR status
+1. **After stack submission:** Call `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` with event type `stack.enqueued` including PR numbers from `exarchos_orchestrate({ action: "list_prs", state: "open" })`
+2. **Monitor merge status:** Use `exarchos_orchestrate({ action: "list_prs", state: "all" })` to check stack/PR status
 3. **On successful merge:** Call `mcp__plugin_exarchos_exarchos__exarchos_event` with `action: "append"` with event type `phase.transitioned` to mark workflow complete
 
 ## Performance Notes

package/skills/claude/delegation/references/pr-fixes-mode.md

@@ -1,155 +0,0 @@
-# PR Feedback Mode (--pr-fixes)
-
-When invoked with `--pr-fixes [PR_URL]`, delegation addresses human review feedback from a pull request instead of implementing from a plan.
-
-## Priority Levels
-
-| Priority | Source | Description |
-|----------|--------|-------------|
-| 1 | `coderabbit:critical` | Critical issues + SPEC COMPLIANCE failures |
-| 2 | `human` | Human reviewer comments (authority over automation) |
-| 3 | `coderabbit:major` | Major issues + CODE QUALITY HIGH items |
-| 4 | `coderabbit:minor` | Minor issues |
-
-## Process
-
-### Step 1: Fetch All PR Feedback
-
-```bash
-# Get full PR details including reviews and comments
-gh pr view <number> --json title,body,state,files,reviewDecision,reviews,comments
-
-# Get issue-level comments (pre-merge check summaries)
-gh issue view <number> --json comments
-```
-
-> Or use GitHub MCP `pull_request_read` and `issue_read` if available.
-
-### Step 2: Parse CodeRabbit Feedback
-
-**2a: Identify CodeRabbit comments** by author = `coderabbitai[bot]`
-
-**2b: Parse line comments by severity label:**
-
-| Label | Priority |
-|-------|----------|
-| `Critical` | 1 |
-| `Major` | 2 |
-| `Minor` | 3 |
-
-Extract from each comment:
-- Severity label (emoji + text)
-- File path and line number
-- Issue description
-- Suggested fix (from Proposed fix section if present)
-
-**2c: Parse pre-merge check summaries:**
-- `Status: FAIL` in Spec Review -> Priority 1
-- `Status: NEEDS_FIXES | BLOCKED` in Quality Review -> Priority 2
-- Extract items from `Missing:`, `Untested:`, `Scope Creep:` lists
-
-**2d: Parse reviews with `CHANGES_REQUESTED`:**
-- Note "Actionable comments posted: N" count
-- Cross-reference with line comments already parsed
-
-### Step 3: Parse Human Comments (Priority 2)
-
-For non-CodeRabbit comments, assign `priority: 2` (human authority over automation).
-
-Skip comments that are:
-- Purely praise/acknowledgment ("LGTM", "Nice work")
-- Questions without action items
-- Already marked resolved
-- From other bots (CI notifications, etc.)
-
-### Step 4: Create Fix Tasks
-
-For each actionable item, create a structured fix task:
-
-| Field | Description |
-|-------|-------------|
-| `id` | `fix-001`, `fix-002`, etc. |
-| `priority` | `1` (critical), `2` (human), `3` (major), `4` (minor) |
-| `source` | `"coderabbit:critical"`, `"human"`, `"coderabbit:major"`, `"coderabbit:minor"` |
-| `severity` | `"Critical"`, `"Major"`, `"Minor"`, or null |
-| `file` | File path |
-| `line` | Line number (if line comment) |
-| `issue` | Problem description |
-| `action` | Required change / suggested fix |
-
-### Step 5: Sort and Display Fix Tasks
-
-Sort by priority (1->4), then by file path for grouping.
-
-### Step 6: Track Fix Tasks
-
-Use TodoWrite to track all fix tasks with priority labels.
-
-### Step 7: Dispatch Fixes (MANDATORY - Priority Order)
-
-**Dispatch sequence:**
-1. Dispatch all P1 (critical) fixes in parallel
-2. Wait for completion
-3. Dispatch all P2 (human) fixes in parallel
-4. Wait for completion
-5. Dispatch all P3 (major) fixes in parallel
-6. Wait for completion
-7. Dispatch all P4 (minor) fixes in parallel
-8. Wait for completion
-
-**Task prompt template:**
-```typescript
-Task({
-  subagent_type: "general-purpose",
-  model: "opus",
-  description: "Fix [P{priority} {severity}]: {issue summary}",
-  prompt: `
-# Task: Fix PR Feedback - {issue summary}
-
-## Priority
-{priority} - {source}
-
-## Context
-PR: {PR_URL}
-Source: {source}
-Original feedback: "{original comment text}"
-
-## Working Directory
-{absolute path to repo}
-
-## Fix Required
-File: {file path}
-Line: {line number if applicable}
-Issue: {issue description}
-Action: {required change}
-
-## TDD Requirements
-1. Write a test that would catch this issue (if applicable)
-2. Verify test fails
-3. Implement the fix
-4. Verify test passes
-
-## Success Criteria
-- [ ] Issue addressed per feedback
-- [ ] Tests pass
-- [ ] No regressions introduced
-`
-})
-```
-
-**CHECKPOINT:** Do NOT proceed to next priority level until all fixes in the current level have completed.
-
-### Step 8: Push and Report
-
-After all fixes complete, commit and push:
-```bash
-git add <fixed-files>
-git commit -m "fix: address PR review feedback"
-git push
-```
-
-Report to user: total fixes by priority, files modified. Then auto-chain to `/exarchos:synthesize` for merge confirmation.
-
-### Handling Missing CodeRabbit Comments
-
-If no CodeRabbit comments found, proceed with human comments only.

package/skills/codex/delegation/references/pr-fixes-mode.md

@@ -1,155 +0,0 @@
-# PR Feedback Mode (--pr-fixes)
-
-When invoked with `--pr-fixes [PR_URL]`, delegation addresses human review feedback from a pull request instead of implementing from a plan.
-
-## Priority Levels
-
-| Priority | Source | Description |
-|----------|--------|-------------|
-| 1 | `coderabbit:critical` | Critical issues + SPEC COMPLIANCE failures |
-| 2 | `human` | Human reviewer comments (authority over automation) |
-| 3 | `coderabbit:major` | Major issues + CODE QUALITY HIGH items |
-| 4 | `coderabbit:minor` | Minor issues |
-
-## Process
-
-### Step 1: Fetch All PR Feedback
-
-```bash
-# Get full PR details including reviews and comments
-gh pr view <number> --json title,body,state,files,reviewDecision,reviews,comments
-
-# Get issue-level comments (pre-merge check summaries)
-gh issue view <number> --json comments
-```
-
-> Or use GitHub MCP `pull_request_read` and `issue_read` if available.
-
-### Step 2: Parse CodeRabbit Feedback
-
-**2a: Identify CodeRabbit comments** by author = `coderabbitai[bot]`
-
-**2b: Parse line comments by severity label:**
-
-| Label | Priority |
-|-------|----------|
-| `Critical` | 1 |
-| `Major` | 2 |
-| `Minor` | 3 |
-
-Extract from each comment:
-- Severity label (emoji + text)
-- File path and line number
-- Issue description
-- Suggested fix (from Proposed fix section if present)
-
-**2c: Parse pre-merge check summaries:**
-- `Status: FAIL` in Spec Review -> Priority 1
-- `Status: NEEDS_FIXES | BLOCKED` in Quality Review -> Priority 2
-- Extract items from `Missing:`, `Untested:`, `Scope Creep:` lists
-
-**2d: Parse reviews with `CHANGES_REQUESTED`:**
-- Note "Actionable comments posted: N" count
-- Cross-reference with line comments already parsed
-
-### Step 3: Parse Human Comments (Priority 2)
-
-For non-CodeRabbit comments, assign `priority: 2` (human authority over automation).
-
-Skip comments that are:
-- Purely praise/acknowledgment ("LGTM", "Nice work")
-- Questions without action items
-- Already marked resolved
-- From other bots (CI notifications, etc.)
-
-### Step 4: Create Fix Tasks
-
-For each actionable item, create a structured fix task:
-
-| Field | Description |
-|-------|-------------|
-| `id` | `fix-001`, `fix-002`, etc. |
-| `priority` | `1` (critical), `2` (human), `3` (major), `4` (minor) |
-| `source` | `"coderabbit:critical"`, `"human"`, `"coderabbit:major"`, `"coderabbit:minor"` |
-| `severity` | `"Critical"`, `"Major"`, `"Minor"`, or null |
-| `file` | File path |
-| `line` | Line number (if line comment) |
-| `issue` | Problem description |
-| `action` | Required change / suggested fix |
-
-### Step 5: Sort and Display Fix Tasks
-
-Sort by priority (1->4), then by file path for grouping.
-
-### Step 6: Track Fix Tasks
-
-Use TodoWrite to track all fix tasks with priority labels.
-
-### Step 7: Dispatch Fixes (MANDATORY - Priority Order)
-
-**Dispatch sequence:**
-1. Dispatch all P1 (critical) fixes in parallel
-2. Wait for completion
-3. Dispatch all P2 (human) fixes in parallel
-4. Wait for completion
-5. Dispatch all P3 (major) fixes in parallel
-6. Wait for completion
-7. Dispatch all P4 (minor) fixes in parallel
-8. Wait for completion
-
-**Task prompt template:**
-```typescript
-Task({
-  subagent_type: "general-purpose",
-  model: "opus",
-  description: "Fix [P{priority} {severity}]: {issue summary}",
-  prompt: `
-# Task: Fix PR Feedback - {issue summary}
-
-## Priority
-{priority} - {source}
-
-## Context
-PR: {PR_URL}
-Source: {source}
-Original feedback: "{original comment text}"
-
-## Working Directory
-{absolute path to repo}
-
-## Fix Required
-File: {file path}
-Line: {line number if applicable}
-Issue: {issue description}
-Action: {required change}
-
-## TDD Requirements
-1. Write a test that would catch this issue (if applicable)
-2. Verify test fails
-3. Implement the fix
-4. Verify test passes
-
-## Success Criteria
-- [ ] Issue addressed per feedback
-- [ ] Tests pass
-- [ ] No regressions introduced
-`
-})
-```
-
-**CHECKPOINT:** Do NOT proceed to next priority level until all fixes in the current level have completed.
-
-### Step 8: Push and Report
-
-After all fixes complete, commit and push:
-```bash
-git add <fixed-files>
-git commit -m "fix: address PR review feedback"
-git push
-```
-
-Report to user: total fixes by priority, files modified. Then auto-chain to `/exarchos:synthesize` for merge confirmation.
-
-### Handling Missing CodeRabbit Comments
-
-If no CodeRabbit comments found, proceed with human comments only.

package/skills/copilot/delegation/references/pr-fixes-mode.md

@@ -1,155 +0,0 @@
-# PR Feedback Mode (--pr-fixes)
-
-When invoked with `--pr-fixes [PR_URL]`, delegation addresses human review feedback from a pull request instead of implementing from a plan.
-
-## Priority Levels
-
-| Priority | Source | Description |
-|----------|--------|-------------|
-| 1 | `coderabbit:critical` | Critical issues + SPEC COMPLIANCE failures |
-| 2 | `human` | Human reviewer comments (authority over automation) |
-| 3 | `coderabbit:major` | Major issues + CODE QUALITY HIGH items |
-| 4 | `coderabbit:minor` | Minor issues |
-
-## Process
-
-### Step 1: Fetch All PR Feedback
-
-```bash
-# Get full PR details including reviews and comments
-gh pr view <number> --json title,body,state,files,reviewDecision,reviews,comments
-
-# Get issue-level comments (pre-merge check summaries)
-gh issue view <number> --json comments
-```
-
-> Or use GitHub MCP `pull_request_read` and `issue_read` if available.
-
-### Step 2: Parse CodeRabbit Feedback
-
-**2a: Identify CodeRabbit comments** by author = `coderabbitai[bot]`
-
-**2b: Parse line comments by severity label:**
-
-| Label | Priority |
-|-------|----------|
-| `Critical` | 1 |
-| `Major` | 2 |
-| `Minor` | 3 |
-
-Extract from each comment:
-- Severity label (emoji + text)
-- File path and line number
-- Issue description
-- Suggested fix (from Proposed fix section if present)
-
-**2c: Parse pre-merge check summaries:**
-- `Status: FAIL` in Spec Review -> Priority 1
-- `Status: NEEDS_FIXES | BLOCKED` in Quality Review -> Priority 2
-- Extract items from `Missing:`, `Untested:`, `Scope Creep:` lists
-
-**2d: Parse reviews with `CHANGES_REQUESTED`:**
-- Note "Actionable comments posted: N" count
-- Cross-reference with line comments already parsed
-
-### Step 3: Parse Human Comments (Priority 2)
-
-For non-CodeRabbit comments, assign `priority: 2` (human authority over automation).
-
-Skip comments that are:
-- Purely praise/acknowledgment ("LGTM", "Nice work")
-- Questions without action items
-- Already marked resolved
-- From other bots (CI notifications, etc.)
-
-### Step 4: Create Fix Tasks
-
-For each actionable item, create a structured fix task:
-
-| Field | Description |
-|-------|-------------|
-| `id` | `fix-001`, `fix-002`, etc. |
-| `priority` | `1` (critical), `2` (human), `3` (major), `4` (minor) |
-| `source` | `"coderabbit:critical"`, `"human"`, `"coderabbit:major"`, `"coderabbit:minor"` |
-| `severity` | `"Critical"`, `"Major"`, `"Minor"`, or null |
-| `file` | File path |
-| `line` | Line number (if line comment) |
-| `issue` | Problem description |
-| `action` | Required change / suggested fix |
-
-### Step 5: Sort and Display Fix Tasks
-
-Sort by priority (1->4), then by file path for grouping.
-
-### Step 6: Track Fix Tasks
-
-Use TodoWrite to track all fix tasks with priority labels.
-
-### Step 7: Dispatch Fixes (MANDATORY - Priority Order)
-
-**Dispatch sequence:**
-1. Dispatch all P1 (critical) fixes in parallel
-2. Wait for completion
-3. Dispatch all P2 (human) fixes in parallel
-4. Wait for completion
-5. Dispatch all P3 (major) fixes in parallel
-6. Wait for completion
-7. Dispatch all P4 (minor) fixes in parallel
-8. Wait for completion
-
-**Task prompt template:**
-```typescript
-Task({
-  subagent_type: "general-purpose",
-  model: "opus",
-  description: "Fix [P{priority} {severity}]: {issue summary}",
-  prompt: `
-# Task: Fix PR Feedback - {issue summary}
-
-## Priority
-{priority} - {source}
-
-## Context
-PR: {PR_URL}
-Source: {source}
-Original feedback: "{original comment text}"
-
-## Working Directory
-{absolute path to repo}
-
-## Fix Required
-File: {file path}
-Line: {line number if applicable}
-Issue: {issue description}
-Action: {required change}
-
-## TDD Requirements
-1. Write a test that would catch this issue (if applicable)
-2. Verify test fails
-3. Implement the fix
-4. Verify test passes
-
-## Success Criteria
-- [ ] Issue addressed per feedback
-- [ ] Tests pass
-- [ ] No regressions introduced
-`
-})
-```
-
-**CHECKPOINT:** Do NOT proceed to next priority level until all fixes in the current level have completed.
-
-### Step 8: Push and Report
-
-After all fixes complete, commit and push:
-```bash
-git add <fixed-files>
-git commit -m "fix: address PR review feedback"
-git push
-```
-
-Report to user: total fixes by priority, files modified. Then auto-chain to `/exarchos:synthesize` for merge confirmation.
-
-### Handling Missing CodeRabbit Comments
-
-If no CodeRabbit comments found, proceed with human comments only.