A battle-tested, AI-assisted development workflow for Claude Code. Pick up a GitHub issue, plan it, implement it, ship a PR — all with structured agent orchestration.
This workflow has been refined over months of daily use on a production codebase. It works with any project — TypeScript, Rust, Python, Go, or anything else.
A set of Claude Code skills (slash commands) that give Claude a structured process for working through GitHub issues:
| Skill | What it does |
|---|---|
/brb-workflow |
Full orchestrator — issue to merged PR |
/brb-pick-issue |
Set up a git worktree and discover/assign a GitHub issue |
/brb-implement |
Plan with architectobot, implement with codecrusher, verify |
/brb-cross-check |
Auto-detect and run all quality checks (typecheck, lint, format, build) |
/brb-raise-pr |
Commit, merge main, push, create a draft PR |
/brb-review-pr |
CodeRabbit-style PR review — gates, analysis, structured findings, optional fixes |
/brb-review-cycle |
Autonomous loop: fix review comments, CI failures, merge conflicts |
/brb-create-issue |
Research codebase, draft a structured issue from a casual description, file it |
| Skill | What it does |
|---|---|
/brb-architectobot |
Analyze codebase, create implementation plans, verify acceptance criteria |
/brb-codecrusher |
Execute implementation plans — write clean, production-ready code |
/brb-memory-keeper |
Capture learnings and gotchas into project memory for future sessions |
/brb-update-workflow |
Pull latest skills from GitHub and update your install |
- Always ask before assuming. Plans require explicit user approval. Ambiguity gets clarified, not guessed at.
- Git worktrees over branches. Work on multiple issues in parallel without stashing or switching.
- Draft PRs always. Never open a non-draft PR. Let CI and reviewers do their thing first.
- Autonomous review cycles. Once a PR is up, the review cycle runs until it's fully clean — no hand-holding.
- Session resume. Start a new session and pick up where you left off — worktrees, draft PRs, and workflow phase are detected automatically.
- Zero config. Skills auto-detect your repo, username, package manager, and default branch. No config files needed.
bash <(curl -fsSL https://raw.githubusercontent.com/graycyrus/claude-workflow/main/install.sh)Choose between:
- Copy — Global (
~/.claude/skills/) — works everywhere, update via/brb-update-workflow - Copy — Project (
.claude/skills/) — per-project, update via/brb-update-workflow - Symlink — Global — clones to
~/.claude/claude-workflow/, symlinks skills.git pull= instant updates.
curl -fsSL https://raw.githubusercontent.com/graycyrus/claude-workflow/main/install.sh | bashgit clone https://github.com/graycyrus/claude-workflow.git /tmp/claude-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/claude-workflow/skills/* ~/.claude/skills/
rm -rf /tmp/claude-workflowRun /brb-update-workflow inside Claude Code — it pulls the latest from GitHub, shows what changed, and updates in place.
cd ~/.claude/claude-workflow && git pullThat's it — symlinks point to the repo, so changes are picked up immediately.
Once installed, the skills are available as slash commands in Claude Code:
# Full workflow — start to finish
/brb-workflow
# Full workflow for a specific issue
/brb-workflow 123
# Individual steps
/brb-pick-issue
/brb-implement 123
/brb-cross-check
/brb-raise-pr 123
/brb-review-cycle 456
You: /brb-workflow
Claude: [detects repo, username, package manager]
[checks branch, syncs upstream, creates worktree]
"Do you want to work on an assigned issue or pick an unassigned one?"
You: pick one for me
Claude: [runs discovery funnel, shows top candidate]
"Issue #87: Add dark mode toggle — priority: medium. Go ahead?"
You: yes
Claude: [assigns issue, loads context, runs architectobot]
[presents implementation plan]
"Here's the plan. Any concerns before I implement?"
You: looks good, go ahead
Claude: [runs codecrusher, implements, verifies, runs checks]
[commits, pushes, creates draft PR]
[enters review cycle — fixes comments, CI, conflicts]
"Everything's clean. Want me to mark the PR as ready?"
- Claude Code CLI installed
- GitHub CLI (
gh) installed and authenticated - Git configured with your identity
The workflow orchestrates three specialized agent skills:
/brb-architectobot— Explores the codebase, creates implementation plans, verifies acceptance criteria/brb-codecrusher— Writes code changes following the approved plan/brb-memory-keeper— Captures learnings and gotchas for future sessions
These ship as part of this repo. The workflow skills (/brb-workflow, /brb-implement) call them automatically, but you can also use them standalone — e.g. /brb-architectobot 123 to plan an issue without running the full workflow.
Skills detect your project setup at runtime — no configuration needed:
| What | How |
|---|---|
| Repo (owner/name) | gh repo view |
| GitHub username | gh api user |
| Package manager | Lockfile detection (bun/pnpm/yarn/npm) |
| Default branch | git symbolic-ref |
| Upstream remote | Checks for upstream remote |
| Available checks | Reads package.json scripts, checks for Cargo.toml |
Detailed reference docs are in docs/:
- Full workflow — complete step-by-step
- Picking up an issue — discovery and assignment
- Working on an issue — plan, implement, verify
- Cross-checking — quality checks
- Pre-commit checks — staging and committing
- Raising a PR — PR creation and review
# Global
rm -rf ~/.claude/skills/brb-{workflow,pick-issue,implement,cross-check,raise-pr,review-pr,review-cycle,create-issue,architectobot,codecrusher,memory-keeper,update-workflow}
# Per-project
rm -rf .claude/skills/brb-{workflow,pick-issue,implement,cross-check,raise-pr,review-pr,review-cycle,create-issue,architectobot,codecrusher,memory-keeper,update-workflow}
# If symlink install, also remove the cloned repo
rm -rf ~/.claude/claude-workflowSee CONTRIBUTING.md. PRs welcome.
MIT