super-board plugin
A Claude Code plugin: cards dropped into Ready on a GitHub Projects board go through build, QA and review and come back as pull requests
- 666 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Agents write code and merge pull requests into the main branch themselves when checks pass
- Hooks and scripts are installed into the project, and the gate may apply allowed database migrations
- The skill needs a gh token with `repo` and `project` scopes, which means write access to the repository and the board
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/super-boardDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Agents write code and merge pull requests into the main branch themselves when checks pass
- Hooks and scripts are installed into the project, and the gate may apply allowed database migrations
- The skill needs a gh token with `repo` and `project` scopes, which means write access to the repository and the board
This is third-party code. Review the repository files before installing.
What it does
super-board turns a GitHub Projects board into a pipeline for a coding agent. You put tasks into the Ready column and run `/super-board run <project>`. Each card then passes three lanes: a builder in a separate worktree makes the smallest safe change, writes tests and opens a draft pull request; a tester gathers evidence and screenshots or bounces the work back to the builder; a reviewer checks it against its own hypotheses and remembers earlier findings. A merge-gate script does the merging, and only after your verify_commands pass on the current base. The package holds nine skills: five you invoke by hand (the orchestrator, problem finder `/super-collect`, page polish loop `/ui-refine-loop`, HTML recap page `/visual`, and `/git-sync`) and four that the board runs. One of the four, `pr-security-review`, checks the diff of every pull request, and any finding sends the card back to build. Six hooks stop, for example, reads of secret files, worktrees created outside `.claude/worktrees/` and deletes outside the project. A cheap model grades each card for difficulty first, then the run flag picks the model for each grade. With `--codex` every lane runs on Codex models.
Who it is for. For developers and small teams who keep tasks on a GitHub Projects board and want to hand an agent a queue of cards instead of chatting one task at a time.
Good fit when
- The board has accumulated clear cards with acceptance criteria and you want them worked through without constant supervision
- You want one order for every change: tests, a tester pass, review and a security check on each pull request before merging
- You want to collect problems from errors, metrics and open pull requests into a document that cards are then made from, using `/super-collect`
- A UI page needs polishing through a critique and fix loop with `/ui-refine-loop`
- You want a single HTML page recapping a branch or a plan with diagrams, using `/visual`
Not a fit when
- You have one to five small tasks: the description points those to `/implement-spec` instead of the board
- Acceptance criteria are vague: run `/super-board lint` first, or the agent guesses what counts as done
- The project has no build and test commands: the merge gate does not run without a non-empty verify_commands
- The repository cannot be trusted to automatic merging: the gate merges a pull request itself once the checks are green
Example request
/super-board run my-appLimitations
You need Claude Code, the gh CLI with `project`, `read:project` and `repo` scopes, dynamic workflows enabled in `/config`, jq, bash 3.2 or newer and Python 3.9 or newer. Set verify_commands in the configuration: without it the merge gate cannot confirm the build.
The plugin ships only the skills. Hooks, scripts and workflows are added by the checks step in `/super-board onboard`, and the one-line curl install does that at once. The hook that blocks direct pushes to the main branch is opt-in. Cloudflare's `security-audit` skill is fetched at install through `npx skills`, and `--no-helper-skills` skips it. The project owner decides which database migrations the gate may apply under the merge policy.
How to disable. If you installed the plugin, run `/plugin uninstall super-board@super-board`. Running workers stop with `/super-board stop`. Hooks and scripts the installer added live in the project's `.claude/` and are removed from the project by hand.
FAQ
How do I install super-board in Claude Code?
Two routes exist. The curl command from the project folder installs skills, hooks and scripts at once. The plugin installs with `/plugin marketplace add EricTechPro/super-board` and `/plugin install super-board@super-board`; afterwards run `/super-board onboard` to add the hooks and scripts.
What does the merge gate do?
It merges a pull request only after your non-empty verify_commands pass on the current base. The check is pinned to the reviewed commit. Then the merge policy and allowed database migrations are applied.
How does `pr-security-review` differ from `security-audit`?
The first runs on every pull request in the QA lane and checks only the diff for vulnerabilities; any finding sends the card back to build. The second runs on request and audits the whole repository, and the board never runs it.
Can it run on Codex models?
Yes. The `--codex` flag moves every lane to Codex models, and `--codex=<model>` pins one model for all cards and skips the difficulty grading. Inside Codex a plain `/super-board run` switches to the Codex ladder itself.
How do I pick a cheaper or costlier mode?
The `--low` and `--high` flags shift the set of models for each card difficulty down or up. Without flags the middle ladder runs.
What protections does the agent have?
Six hooks block reads of secret files and SSH keys, writing a live-looking API key into a file, creating worktrees outside `.claude/worktrees/` and deleting outside the project. Direct pushes to the main branch are blocked if you turn that on.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
A plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
A universal workflow plugin for Claude Code: 7 agents, 26 commands, 14 skills and 14 hooks for any project
Claude Code Blueprint: 12 agents, 19 skills, 16 hooks and 6 CLAUDE.md rules, copy what you need or install a preset
Claude Code plugins: plan, work and review commands, subagents, hooks and writing skills in a practical minimalism spirit.
22 skills for the full Claude Code project lifecycle: setup and task scope, code review, pre-push checks and session notes.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| super-board (this card) | no | 666 | |
| Eigenwise Toolshed | no | 284 | six independent plugins including a project map and a task board, without a merge pipeline |
| gstack | no | 141,385 | a virtual team of roles for a dialog with an agent, without a board or merge gate |
README in short
The description opens with the promise "add tasks, walk away", then lists requirements, install commands and the two routes, plugin or script. Tables break down the nine skills, the commands, the hooks and the model ladder by card difficulty. Links to the project site, the skill map and the release notes close it.