Skip to content

Add @claude-triggered multi-agent issue-fix pipeline - #122

Merged
fishjojo merged 5 commits into
mainfrom
feat/agentic-issue-fix-workflow
Jun 3, 2026
Merged

Add @claude-triggered multi-agent issue-fix pipeline#122
fishjojo merged 5 commits into
mainfrom
feat/agentic-issue-fix-workflow

Conversation

@fishjojo

@fishjojo fishjojo commented Jun 3, 2026

Copy link
Copy Markdown
Owner

Summary

Makes the manual @claude mention the single path for resolving issues (bug fixes
and feature implementations), running a gated multi-agent pipeline. Removes the older
label-triggered single-agent auto-fix mechanics entirely.

Flow when a trusted maintainer (OWNER/MEMBER/COLLABORATOR) @claudes on an issue:

Stage 0: bug-verifier  ← single agent, reproduces the bug / checks a feature is actionable
   ├─ confirmed / actionable  → multi-agent pipeline
   │      context-builder → fix-planner
   │      → fix-implementer/fix-verifier loop (≤4 iters) → draft PR
   └─ not_reproducible / not_a_bug / needs_info / out_of_scope
          → comment with verdict + evidence, STOP (no code, no PR)

Added

  • .claude/commands/fix-issue.md — shared orchestrator command. Stage 0 is a
    single-agent verification gate; the multi-agent pipeline runs only on a confirmed
    bug / actionable feature, otherwise it comments the verdict and stops. No green-washing;
    bounded iteration cap.
  • .claude/agents/bug-verifier (reproduction gate, with python/pytest/pip),
    context-builder, fix-planner, fix-implementer, fix-verifier (all Opus; effort via
    role prompts).
  • .github/workflows/claude.yml — the @claude path now allows the Task tool +
    read tools and routes issue fix/feature requests through the verification-gate +
    multi-agent pipeline. Existing auto-review handling (review threads, workflow-permission
    guard, web tools) preserved unchanged.

Removed (old auto-fix mechanics)

  • .github/workflows/claude-verify-bug.yml and .github/workflows/claude-fix-bug.yml
    — the label-triggered read-only-verify → dispatch-fix workflows (from Auto-fix bug-labeled issues: verify, fix, open PR #121).
  • The dispatch-verify job in claude-issue-triage.yml — triage now only applies
    labels and never auto-triggers a fix.

There is no longer any label-triggered auto-fix; @claude is the only trigger.

Notes

  • Rebased onto latest main; the standalone webhook bot from an earlier revision of this
    branch was removed from the PR.

🤖 Generated with Claude Code

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b8970c89c1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread github-issue-bot/src/solver.js Outdated
Comment thread github-issue-bot/src/policy.js Outdated
Comment thread github-issue-bot/src/policy.js Outdated
Comment thread github-issue-bot/src/server.js Outdated
Comment thread github-issue-bot/src/solver.js Outdated
Comment thread github-issue-bot/src/solver.js Outdated
Route @claude fix / feature requests on issues (trusted maintainers only,
gated by claude.yml's existing if:) through a gated multi-agent pipeline.

- .claude/commands/fix-issue.md: shared orchestrator command. Stage 0 runs a
  single-agent bug-verifier gate; the multi-agent pipeline (context-builder ->
  fix-planner -> orchestrated fix-implementer/fix-verifier loop) runs only on a
  confirmed bug / actionable feature, otherwise it comments and stops.
- .claude/agents/: bug-verifier (reproduction gate, with python/pytest/pip),
  context-builder, fix-planner, fix-implementer, fix-verifier.
- .github/workflows/claude.yml: the @claude path now allows the Task tool +
  read tools and routes issue fix/feature requests through the pipeline,
  preserving the existing auto-review handling. The bug-label auto path
  (claude-verify-bug.yml / claude-fix-bug.yml) is untouched.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec9f3dd628

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .github/workflows/claude.yml Outdated
Comment thread .claude/agents/bug-verifier.md Outdated
Comment thread .claude/commands/fix-issue.md Outdated
Comment thread .claude/agents/fix-verifier.md Outdated
The @claude verification-gate + multi-agent pipeline (claude.yml +
.claude/commands/fix-issue.md) is now the sole way fixes/features are
implemented. Remove the older single-agent auto-fix mechanics:

- delete claude-verify-bug.yml and claude-fix-bug.yml (the bug-label
  read-only-verify -> dispatch-fix workflows).
- drop the dispatch-verify job from claude-issue-triage.yml so triage only
  applies labels and never auto-triggers a fix.
- update claude.yml comment: @claude on an issue is the only fix/feature path.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ore tests

- bug-verifier: drop raw git/gh; restrict GitHub access to the read-only
  ./scripts/gh.sh wrapper and add untrusted-input (prompt-injection) hardening,
  so the pre-gate verifier cannot push/comment with the job's write token.
- fix-issue.md: add a Reporting convention so GIT: harness never calls gh/git
  (including the gate-failure and non-convergence stops) and returns the verdict
  as its final message; only GIT: self posts comments / opens PRs.
- fix-verifier / fix-implementer: add Bash(pip:*) and a build-first step so a
  fresh/unbuilt checkout (notably the feature path) is built per CLAUDE.md
  instead of being reported as a test failure.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ddbf513df3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .claude/agents/context-builder.md Outdated
Comment thread .claude/commands/fix-issue.md Outdated
The bug-verifier stays read-only and never comments; the orchestrator owns the
user-facing report. Make that explicit and have the verifier emit a
self-contained, comment-ready summary (for not_reproducible / needs_info /
out_of_scope, stating what would unblock the issue) that the orchestrator posts
verbatim — an issue comment in GIT: self, or its final message in GIT: harness.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8e4602b02f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .claude/agents/fix-planner.md Outdated
Comment thread .claude/agents/fix-verifier.md
…er, unique branch

- context-builder: drop raw gh/git; restrict to ./scripts/gh.sh + non-mutating
  git verbs (log/show/diff/blame/status), with untrusted-input hardening.
- fix-planner: drop raw gh; read-only via ./scripts/gh.sh only, plus hardening.
- fix-verifier: make the original-reproduction check conditional — bugs rerun
  the repro, features run the plan's acceptance exercise instead (no repro
  exists for a feature).
- fix-issue.md: before opening a PR, reuse/skip an existing open bot PR for the
  issue, and append a unique suffix when the branch ref already exists so a
  re-trigger does not fail with a non-fast-forward push.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@fishjojo
fishjojo merged commit 6290f36 into main Jun 3, 2026
21 checks passed
@fishjojo
fishjojo deleted the feat/agentic-issue-fix-workflow branch June 19, 2026 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant