Skip to content

Add a github-issue workflow that reads a linked issue and lands a peer-reviewed fix - #375

Merged
tildesrc merged 2 commits into
mainfrom
panopticon/github-issue-workflow
Aug 13, 2026
Merged

Add a github-issue workflow that reads a linked issue and lands a peer-reviewed fix#375
tildesrc merged 2 commits into
mainfrom
panopticon/github-issue-workflow

Conversation

@tildesrc

@tildesrc tildesrc commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Adds a new built-in workflow, github-issue, whose task memo is a link to a GitHub issue. The workflow reads that issue, plans and implements a fix, opens a PR that closes it, and lands it after a peer review.

Design

GithubIssue subclasses GithubForgeWorkflow, so it inherits the forge plumbing (gh tool, image layer, open-pr/babysit-ci/babysit-merge). It's a near-twin of github-peer-reviewed — the full PLANNING → ITERATING → REVIEW → MERGING → COMPLETE graph with a peer-review gate — specialised the way github-dependabot specialises for an input-URL memo:

  • PLANNING reads the linked issue via a new read-issue skill (gh issue view <url> --comments, reading the URL from the task memo, and noting the issue number so the PR later closes it). It gates a new module-level issue-understood responsibility that forces the plan.md to engage with the issue on five axes: the reported problem, the root cause, how the fix is reproduced/confirmed, the fix approach, and the tests that prove it.
  • ITERATING opens a fresh PR (inherited open-pr) whose body closes the issue (Closes #<n>). Because the PR URL is produced here (not a known input like Dependabot's), url-recorded stays in ITERATING — the same 7 responsibilities as github-peer-reviewed.
  • REVIEW is the peer-review gate (pr-reviewed) before the merge queue.
  • MERGING is unchanged (agent-driven merge-queue shepherding).

The three inherited forge skills are reused verbatim; only read-issue is added on top.

Scope

Pure workflow addition — no core/taskservice/sessionservice changes and no migrations. Discovery auto-registers the dropped-in module; it's also re-exported from the workflows package and added to the default-wiring assertion.

🤖 Generated with Claude Code

Panopticon Agent and others added 2 commits August 13, 2026 17:16
The task memo is a link to a GitHub issue. GithubIssue subclasses
GithubForgeWorkflow — the same collapsed PLANNING → ITERATING → MERGING →
COMPLETE graph as github-self-reviewed (the user self-reviews the fix and
approves it by advancing out of ITERATING), specialised for issue-fixing:

- PLANNING reads the issue (new `read-issue` skill: `gh issue view`, note the
  number so the PR closes it) and gates a new `issue-understood` responsibility
  forcing the plan to cover the problem, root cause, reproduction/confirmation,
  fix approach, and tests.
- ITERATING opens a fresh PR (inherited `open-pr`) whose body closes the issue,
  so `url-recorded` stays in ITERATING (unlike github-dependabot, whose PR URL
  is a known input). MERGING is unchanged.

Registered by discovery automatically; re-exported from the workflows package
and added to the default-wiring assertion.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Model GithubIssue on GithubPeerReviewed rather than GithubSelfReviewed: a peer
reviews the PR (the REVIEW state, `pr-reviewed`) before it reaches the merge
queue. The issue-specific parts are unchanged — the `read-issue` skill and the
`issue-understood` PLANNING responsibility, and `url-recorded` stays in
ITERATING (the PR is opened there).

Graph is now PLANNING → ITERATING → REVIEW → MERGING → COMPLETE.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tildesrc tildesrc changed the title Add a github-issue workflow that reads a linked issue and lands a fix Add a github-issue workflow that reads a linked issue and lands a peer-reviewed fix Aug 13, 2026
@tildesrc
tildesrc marked this pull request as ready for review August 13, 2026 19:47
@tildesrc
tildesrc merged commit 9dbb4ed into main Aug 13, 2026
3 checks passed
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