Ship GitHub issues one at a time through Claude Code and CI
At a glance
A solo founder built Passband through an issue-driven Claude Code pipeline with automated tests and human merge review. This workflow is listed under issue-driven-development, coding-agents, continuous-integration, human-review.
- Agents / tools
- Claude Code, GitHub, Playwright, CI
Building a tool for these workflows? See weekly rates.
What they did
Joe Graham wrote GitHub issues with acceptance criteria. An orchestrator selected the highest-priority unblocked issue, and Claude Code implemented it in a sandboxed branch. CI ran the build and 12 Playwright end-to-end tests. Failed runs retried with error context; passing changes went to Graham for review and squash-merge. He limited work in progress to one ticket.
How it went
He reports shipping more than 30 tickets and two publishing integrations. Small tasks averaged about 45 minutes from ticket to merged pull request; medium tasks took two to three hours.
Worth knowing
A reader subsequently reported a broken dashboard. Graham traced it to a missing secret that prevented his database migration pipeline from running.