Skip to content

feat(exodia)!: collapse turbo-fix + fix-pipeline into one /exodia:fix (v3.0.0) #305

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ANcpLua merged 2 commits into from
Jun 10, 2026
Merged

feat(exodia)!: collapse turbo-fix + fix-pipeline into one /exodia:fix (v3.0.0) #305

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f4d289f
feat(exodia)!: collapse turbo-fix + fix-pipeline into one /exodia:fix…
ANcpLua Jun 10, 2026
31d197e
chore: delete empty .claude/settings.json (invalid JSON, zero-byte rot)
ANcpLua Jun 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .claude-plugin/marketplace.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@
},
{
"name": "exodia",
"description": "Multi-agent workflow orchestration (9 commands + 2 skills: eight-gates, hades): fix, turbo-fix, fix-pipeline, tournament, mega-swarm, deep-think, batch-implement, red-blue-review, baryon-mode. Hades, eight-gates, and red-blue-review use Teams API for reactive collaboration.",
"version": "2.2.2",
"description": "Multi-agent workflow orchestration (7 commands + 2 skills: eight-gates, hades): fix, tournament, mega-swarm, deep-think, batch-implement, red-blue-review, baryon-mode. Hades, eight-gates, and red-blue-review use Teams API for reactive collaboration.",
"version": "3.0.0",
Comment on lines +31 to +32
"source": "./plugins/exodia"
},
{
Expand Down
Empty file removed .claude/settings.json
View file
Open in desktop
Empty file.
2 changes: 1 addition & 1 deletion plugins/council/commands/council.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ early saves tokens but eliminates that reactive reconciliation.

- Simple factual questions → just ask directly
- Single-file code edits → use feature-dev
- P0 bugs → use exodia:turbo-fix
- P0 bugs → use exodia:fix `<issue>` P0 maximum
- Cleanup tasks → use exodia:hades

## Cost profile
Expand Down
4 changes: 2 additions & 2 deletions plugins/exodia/.claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "exodia",
"version": "2.2.2",
"description": "Multi-agent workflow orchestration: 9 commands (fix, turbo-fix, tournament, mega-swarm, red-blue-review, baryon-mode...) plus eight-gates and hades skills using the Teams API for reactive work.",
"version": "3.0.0",
"description": "Multi-agent workflow orchestration: 7 commands (fix, tournament, mega-swarm, red-blue-review, baryon-mode...) plus eight-gates and hades skills using the Teams API for reactive work.",
"author": {
"name": "ANcpLua",
"url": "https://github.com/ANcpLua"
Expand Down
8 changes: 3 additions & 5 deletions plugins/exodia/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,12 @@
# exodia

Multi-agent workflow orchestration. 9 commands + 2 skills (eight-gates, hades).
Multi-agent workflow orchestration. 7 commands + 2 skills (eight-gates, hades).

## Commands

| Command | Agents | Pattern | Best For |
|---------|--------|---------|----------|
| `/exodia:turbo-fix` | 13 | Phased pipeline | P0 critical bugs |
| `/exodia:fix` | 8-16 | Configurable pipeline | Any bug fix |
| `/exodia:fix-pipeline` | 7 | Systematic pipeline | Audit findings |
| `/exodia:fix` | 8-14 | Gated pipeline (`severity` P0-P3, `parallelism` standard\|maximum) | Any bug — ad-hoc, P0 (add `maximum`), or audit findings (auto-inherited) |
| `/exodia:tournament` | N+2 | Competition | Quality optimization |
| `/exodia:mega-swarm` | 6-12 | All parallel | Codebase audit |
| `/exodia:deep-think` | 5 | Multi-perspective | Analysis before action |
Expand All @@ -29,7 +27,7 @@ Multi-agent workflow orchestration. 9 commands + 2 skills (eight-gates, hades).
1. Go all-in on objective → /exodia:eight-gates "ship v2.0" . 8
2. Audit the codebase → /exodia:mega-swarm mode=quick
3. Exterminate warnings → /exodia:baryon-mode path/to/Solution.sln
4. Fix critical issues → /exodia:turbo-fix (P0) or /exodia:fix (P1/P2)
4. Fix any issue → /exodia:fix "issue" (add `maximum` for P0; auto-inherits audit findings)

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the severity before maximum

For users following this migration example for a P0, adding only maximum after the issue does not actually select maximum mode because fix parses $1 as severity and $2 as parallelism (plugins/exodia/commands/fix.md:11-13). /exodia:fix "issue" maximum therefore leaves $2 at its default standard and gives the workflow an invalid severity instead of the intended P0 maximum pipeline; the example should show P0 maximum.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Show the full P0 maximum invocation

For the P0 case this example tells users to add only maximum, but fix.md still treats $1 as severity and $2 as parallelism. A user following this as /exodia:fix "issue" maximum will pass maximum as the severity and leave parallelism at the standard default, so the max-only agents described by the migration will not run; the example should show P0 maximum.

Useful? React with 👍 / 👎.

5. Security review → /exodia:red-blue-review scope=security
6. Architectural decisions → /exodia:deep-think mode=architecture
7. Batch implement features → /exodia:batch-implement type=endpoints
Expand Down
214 changes: 0 additions & 214 deletions plugins/exodia/commands/fix-pipeline.md
View file
Open in desktop

This file was deleted.

30 changes: 13 additions & 17 deletions plugins/exodia/commands/fix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
description: "IF bug fix needed THEN use this. 4 gated phases, 8 agents (standard) or 16 (maximum). For P0 critical → turbo-fix. From audit findings → fix-pipeline."
description: "IF a bug needs fixing THEN use this — the one exodia fix command. 4 gated phases (analyze → design → implement → verify). Args: severity P0|P1|P2|P3 and parallelism standard|maximum (use maximum for P0 emergencies). Auto-inherits audit findings.json from a prior mega-swarm / eight-gates run when present."

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Don't claim eight-gates auto-inheritance

This expanded description promises auto-inheritance after an eight-gates run, but the eight-gates checkpoint path caches its merged findings with session-state.sh artifact add "findings" (plugins/exodia/skills/eight-gates/templates/gate-04-checkpoint.md line 22), which writes .eight-gates/artifacts/findings, not the .eight-gates/artifacts/findings.json file that fix reads. Users coming from eight-gates therefore get no injected fix/files context and the consolidated command falls back to rediscovery.

Useful? React with 👍 / 👎.

allowed-tools: Task, Bash, TodoWrite
effort: high
---
Expand Down Expand Up @@ -35,9 +35,8 @@ FIX LEAD (You — Orchestrator)
│ └── devils-advocate ← skip if $4=true
│ └── GATE 2 → PROCEED | HALT
│
├─ Phase 3: IMPLEMENTATION (standard: 1, maximum: 3)
│ ├── tdd-implementer
│ ├── test-writer ← maximum only
├─ Phase 3: IMPLEMENTATION (standard: 1, maximum: 2)
│ ├── tdd-implementer ← atomic: owns tests AND code
│ └── docs-updater ← maximum only
│ └── GATE 3 → PROCEED | HALT
│
Expand Down Expand Up @@ -294,30 +293,27 @@ Select best solution. Proceed.

## PHASE 3: IMPLEMENTATION

Standard: 1 TDD implementer. Maximum: 3 agents.
Standard: 1 atomic TDD implementer. Maximum: + docs-updater (read-only, in parallel).

### tdd-implementer (standard)
### tdd-implementer (atomic — owns tests AND code)

> subagent: feature-dev:code-architect | model: opus
>
> IMPLEMENT the approved solution. TDD:
> IMPLEMENT the approved solution with atomic TDD. ONE agent owns tests and code —
> never split test-writing from implementation, they diverge:
>
> 1. Write failing test → 2. Minimal fix → 3. Verify pass → 4. Refactor
> 1. Write failing test (RED) — run it, confirm failure
> 2. Minimal fix (GREEN) — run it, confirm pass
> 3. Edge-case + regression tests
> 4. Refactor — tests stay green
>
> Output: Files changed + verification results

### test-writer <- maximum only

> subagent: feature-dev:code-architect
>
> WRITE TESTS FIRST: failing unit test, edge cases, regression test.
> DO NOT implement the fix. Output: Test files with paths
> Output: Changed files with diffs + test results

### docs-updater <- maximum only

> subagent: Explore
>
> CHECK what docs need updating: README, API docs, CHANGELOG, code comments.
> CHECK what docs need updating: README, API docs, CHANGELOG, code comments. Read-only.
> Output: Documentation updates needed

---
Expand Down
4 changes: 2 additions & 2 deletions plugins/exodia/commands/mega-swarm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
description: "IF codebase audit or release readiness check THEN use this. 6-12 agents scan in parallel. Full(12), quick(6), focused(8). Feed findings into fix-pipeline."
description: "IF codebase audit or release readiness check THEN use this. 6-12 agents scan in parallel. Full(12), quick(6), focused(8). Feed findings into fix (auto-inherited)."
allowed-tools: Task, TodoWrite
effort: high
---
Expand Down Expand Up @@ -187,4 +187,4 @@ AUDIT GATE:
| # | Category | Issue | Location |
|---|----------|-------|----------|

**Next:** `/fix-pipeline "[P0 issue]"`
**Next:** `/exodia:fix "[P0 issue]"` — it auto-inherits these findings from `findings.json`.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pass the finding id to preserve audit inheritance

This replacement points audit users at /exodia:fix "[P0 issue]", but the consolidated fix command still says to filter prior findings by finding.id matching $0 (plugins/exodia/commands/fix.md:53), and the SessionStart index exposes ids separately from titles. In the common mega-swarm flow where the user copies the issue title from this report, the lookup will miss and the advertised auto-inheritance of fix, files, and severity will not happen; either instruct users to pass the finding id or make fix match titles/scope too.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pass the persisted finding id to fix

After a mega-swarm run, the persisted JSON includes an id for each finding, and /exodia:fix only injects prior context when finding.id matches $0 (fix.md line 53). This new handoff tells users to pass the rendered P0 issue title from the report table, which has no id column; in that scenario the match misses and fix re-discovers the issue instead of using the stored fix, files, and severity.

Useful? React with 👍 / 👎.

Loading
Loading