super-board is an MIT-licensed automation layer for Claude Code that turns a GitHub Projects board into a self-draining build, QA and review pipeline, built for developers and small teams who would rather write task cards than shepherd every pull request by hand.

What it is

super-board installs into a project folder as a set of Claude Code skills, slash commands and guard hooks. It ships eight skills — five that you type and three that the board runs on its own — alongside nine commands and six hook scripts. The skills span orchestration (/super-board), problem collection (/super-collect), a page-level critique loop (/ui-refine-loop), single-page HTML reporting (/visual) and Git hygiene (/git-sync), while a three-lane rotation of /super-build, /super-qa and /super-review does the per-task work. It lives in the Claude Code ecosystem and runs against a GitHub Projects kanban board, with Codex and OpenCode documented as supported hosts in docs/hosts.md.

The problem it solves is the handoff between a backlog card and a merged pull request. Normally a person acts as dispatcher: reading the card, prompting a coding assistant, checking the result, opening the PR, chasing review. super-board replaces that manual relay with a board that drains itself. Cards placed in Ready are planned into waves, built in isolated worktrees, tested for evidence, reviewed against a merge gate, and merged when green — the loop described in the project's own summary as "add tasks, walk away, get merged PRs with proof."

Key capabilities

• /super-board acts as orchestrator: it plans waves, runs the Build → QA → Review cycle, and merges when the result is green.
• The three board-run lanes are distinct: /super-build opens a worktree and makes the smallest safe change with tests and a draft PR; /super-qa collects evidence, checks for test gaps and screenshots, or bounces work back to Build; /super-review owns its hypotheses, remembers prior findings and holds the merge gate.
• /super-collect sweeps Sentry, PostHog, issues, PRs and architecture for problems and files verified Backlog cards, with a super-collect --since 30d flag for the lookback window.
• Six Python-stdlib guard hooks enforce boundaries automatically: guard-worktree-path confines git worktree add to .claude/worktrees/, guard-secrets blocks reading or piping dotenv files, SSH keys and credential files, guard-key-literals blocks a live-looking API key written into a file, and guard-delete-outside blocks rm, find -delete and git clean aimed outside the project, ~ or /.
• /super-board onboard runs an eight-step setup — Checks, GitHub, Board, Branch, AGENTS.md, Policies, Bug sources, Review — and resumes if interrupted.
• /visual [recap|plan|path] produces a single HTML page covering a branch recap, a plan, or a codebase map with diagrams.
• Run options include run --low, run --high and run --codex, with /super-board status for a read-only snapshot and /super-board stop to halt workers.

Who uses it and how

• Individual developers and small teams who already track work as cards in a GitHub Projects kanban and want Ready drained without dispatching each task by hand.
• Teams standardising on Claude Code as their agent host, including groups that also run Codex or OpenCode against the documented supported versions, sign-in flows and known gaps.
• Projects that need a reviewable trail rather than a bare diff: the QA lane produces evidence and screenshots, and the review lane carries prior findings forward.
• Teams wanting bug intake without a human screener, using /super-collect to turn Sentry, PostHog, issue and PR signals into verified Backlog cards.
• Shops with an existing calibrate skill installed can opt into post-run learning, which applies only to explicitly permitted canonical skill files after verified selected work completes.

Getting started

Run curl -fsSL https://raw.githubusercontent.com/EricTechPro/super-board/main/get.sh | bash inside your project folder, or install it as a plugin with /plugin marketplace add EricTechPro/super-board followed by /plugin install super-board@super-board. Follow with /super-board onboard and then /super-board run my-app.

How it compares

No paid products or directly comparable tools are named in the material provided, so super-board stands alone in this registry as a board-driven build, QA and review loop for Claude Code. Its only named neighbours are the skill libraries it builds on — Matt Pocock skills, ponytail, impeccable and humanizer — which it consumes rather than competes with.

When to use it — and when not to

A self-hoster needs Claude Code plus gh, jq, bash 3.2+ and Python 3.9+, all verified by the installer, and must run the onboard Checks step to install the guard hooks, scripts and workflows, because the plugin distribution ships the skills only. It is a poor fit for teams not on GitHub Projects, or for anyone wanting a graphical, managed product rather than a set of slash commands driven from a terminal. The README is dense and command-first, assumes familiarity with worktrees and agent hooks, and leans on a documentation site and video for the conceptual walkthrough, so expect a real onboarding session before the board runs unattended.

curl -fsSL https://raw.githubusercontent.com/EricTechPro/super-board/main/get.sh | bash

/plugin marketplace add EricTechPro/super-board
/plugin install super-board@super-board

curl -fsSL https://raw.githubusercontent.com/EricTechPro/super-board/main/get.sh | bash

/super-board onboard

/super-board run my-app

/super-board onboard          # 8-step setup, resumes
/super-board lint             # vague ACs?
/super-board status           # read-only snapshot
/super-board run <slug>       # drain the board
/super-board stop             # stop workers
/super-collect [source]       # file problems to Backlog
/ui-refine-loop <route>       # polish one page
/visual [recap|plan|path]     # one HTML page
/git-sync                     # commit, pull, push