super-board README

项目的 README,来自 github.com/EricTechPro/super-board。合并为一个 markdown 文件:README.md。

super-board kanban logo

super-board

Add tasks, walk away, get merged PRs with proof.

Stop babysitting coding agents: cards you drop in Ready come back as tested, reviewed PRs.

9 skills (5 you type, 4 the board runs) · 9 commands · 6 guard hooks

Version Host License

🌐 Live site: erictechpro.github.io/super-board

⭐ Star this repo if it helps · Join the builders using this → weekly live calls, setup help · ▶ Watch the walkthrough

Install · Quick start · How it works · Skills · Commands · Guards

The super-board skill map: open the interactive version

The skill map. Click it for the live version: zoom, pan, open any node.

Install

Before you start:

In your project folder:

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

Or as a Claude Code plugin:

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

[!NOTE] The plugin ships the skills only. Run /super-board:super-board onboard and its 🔍 Checks step adds the guard hooks, scripts and workflows. Needs Claude Code, gh, jq, bash 3.2+ and Python 3.9+; the installer checks.

Security

Two security skills come with every install, and they stay separate:

Skill Runs Covers
pr-security-review On every PR, inside the QA lane. Each finding fails QA and goes back to Build. The PR's diff against its base: high-confidence, exploitable bugs only. From Anthropic's claude-code-security-review.
security-audit Only when you ask (/security-audit). The board never runs it. The whole repository, in depth. From Cloudflare's security-audit-skill, fetched at install with npx skills.

--no-helper-skills skips the security-audit download; /super-board onboard adds it later. Claude Code's built-in /security-review is left as it is.

Running from Codex or OpenCode? See supported hosts for tested versions, sign-in and gaps.

Optional post-run learning can delegate an already installed calibrate skill after verified selected work completes. It applies only to explicitly permitted existing canonical skill files; the package bundles no private skill. See post-run calibration.

Quick start

1. Install

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

2. Onboard

/super-board onboard

Checks · GitHub · Board · Branch · AGENTS.md · Policies · Bug sources · Review. Enter takes the recommended answer.

3. Run

/super-board run my-app

Add cards to Ready. The board drains on its own.

How it works

Which path? Clear idea, foggy idea or bugs: the routing rule says what to run, and when 1–5 tickets go to /implement-spec instead of the board.

Watch I Built a Self-Improving Software Factory by Eric Tech on YouTube

▶ Watch on YouTube: I Built a Self-Improving Software Factory

Skills

9 skills (5 you type, 4 the board runs). Uses Matt Pocock skills, ponytail, impeccable, humanizer, Anthropic's security review and Cloudflare's security-audit.

You type — 5 skills

Skill What it does
/super-board Orchestrator: plans waves, runs Build → QA → Review, merges when green.
/super-collect Finds problems, verifies them, writes a findings doc for /to-spec and /to-tickets.
/ui-refine-loop Critique → refine loop that polishes one page or component.
/visual One HTML page: branch recap, plan, or codebase map with diagrams.
/git-sync Commit per logical change, merge-pull, push without force, report.

The board runs — 4 skills

Skill What it does
/super-build Builder lane: worktree, smallest safe change, tests, draft PR.
/super-qa Tester lane: evidence, test-gap check, screenshots, or bounce to Build.
/super-review Reviewer lane: own hypotheses, remembers prior findings, merge gate.
/pr-security-review Security pass on every PR diff; super-qa runs it, findings fail QA.

Each name links to that skill's README. Adding a skill? Write its SKILL.md and README.md, add a line to skills/families.json, and this table updates itself.

Commands

/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]       # find problems → findings doc → /to-spec
/ui-refine-loop <route>       # polish one page
/visual [recap|plan|path]     # one HTML page
/git-sync                     # commit, pull, push

Flags: run --low|--high · run --codex[=<model>] · super-collect --since 30d

Guards & hooks

Run automatically once installed. Python stdlib, JSON in, JSON out.

guard-worktree-path Blocks git worktree add outside .claude/worktrees/
guard-secrets Blocks reading or piping dotenv files, SSH keys and credential files; key names via super-board-env-check.sh
guard-key-literals Blocks a live-looking API key written into a file; flags one already there
guard-delete-outside Blocks rm, find -delete and git clean aimed outside the project, ~ or /
guard-protected-push Opt-in (onboard asks, or install.sh --protect-main): blocks direct and force pushes to main/master/base
README sync Regenerates the skill table; pre-commit and PostToolUse hooks keep it fresh
cleanup-wt Removes merged worktrees and branches after each merge and at session start, with a recovery file
merge gate Merges only after the current base plus your non-empty project verify_commands pass (missing checks halt setup), pinned to the reviewed commit; applies merge_policy and runs allowed DB migrations

Models

A cheap router grades each card easy, medium or hard first; the run flag picks the model for each grade. With --codex, every lane runs on Codex GPT models instead of Claude.

Command Router Easy card Medium card Hard card
/super-board run Haiku 4.5 Sonnet 5.5 Opus 5.5 session model
/super-board run --low Haiku 4.5 Haiku 4.5 Sonnet 5.5 Opus 5.5
/super-board run --high Sonnet 5.5 Opus 5.5 Opus 5.5 Opus 5.5
/super-board run --codex gpt-6-luna gpt-6.1-sol gpt-6.1-sol gpt-6-astra
/super-board run --codex --low gpt-6-luna gpt-6-luna gpt-6.1-sol gpt-6.1-sol
/super-board run --codex --high gpt-6-luna gpt-6-astra gpt-6-astra gpt-6-astra

/super-board run --codex=<model> pins one model for every card and skips the router.

Run inside Codex? plain /super-board run switches to the Codex ladder by itself. Codex has no /super-board command: it finds skills in .agents/skills/ (symlinks followed), so link .claude/skills/super-board there and type $super-board run.

Writing standard

Commits, tickets, PR bodies and comments all follow one writing standard, in the pack and in every project it is installed into.

Upgrading from 2.x
  1. Re-run the install line.
  2. Run /super-board onboard; step 1 upgrades for you and keeps a backup.
  3. Try board-migrate --dry-run on a copy of your board first.

Full notes

Credits

MIT © Eric Tech (LICENSE). Built on obra/superpowers, mattpocock/skills, BuilderIO/skills and tt-a1i/archify. pr-security-review is ported from anthropics/claude-code-security-review (MIT © 2025 Anthropic, notice); security-audit is cloudflare/security-audit-skill (MIT © 2025-2026 Cloudflare, Inc.), installed from its own repo, not bundled.


Live site · Skill map · Writing standard · Setup simulator · Impeccable map · pstack map · Security audit map · Release notes · Release checks · YouTube walkthrough

Made by Eric Tech

Worker skill availability

Setup and dispatch resolve real, nonempty SKILL.md files for the actual Claude or Codex host. Missing required skills halt before claims or workers; lockfiles and arbitrary plugin caches do not count. The shared registry in scripts/super-board-skills-ready.py owns lane dependencies, overrides and the two declared ponytail fallbacks. The QA lane requires the bundled pr-security-review; Cloudflare's security-audit is an optional QA entry, so a missing copy never halts a run. Setup's full helper union may be red while a selected card is runnable. Read-only checks never install; explicit onboard repair rechecks files after installation.

The CLI accepts --home <fixture-home> and --catalog <active-skills.json>. Launchers accept the same inventory through SUPER_BOARD_SKILLS_HOME and SUPER_BOARD_SKILLS_CATALOG; neither changes the actual host. Catalog shape: {"host":"codex","skills":[{"name":"vendor:skill","path":"/exact/SKILL.md", "enabled":true,"scope":"project","project_root":"/exact/project"}]}. User entries use scope:"user". Restart explicitly after repairing missing skills; readiness certifies availability, not their content or external tools.

super-board (EricTechPro/super-board)

正在搜索数据库…

这是什么?super-board 是用于 Claude Code 的自主 Build → QA → Review 循环:你把卡片放进 Ready 列,系统就会规划工作、编写代码、进行测试、审查,并在全部通过后合并 PR。
这是独立应用,还是在 Claude Code 里运行?它是一个 Claude Code 的 skill/插件包,而不是独立应用程序。它会向你现有的项目添加 8 个 skill(5 个由你手动输入,3 个由看板自动运行)、9 个斜杠命令和 6 个防护钩子。
我怎么在项目里把它跑起来?在项目文件夹中运行一行安装命令(或将其安装为 Claude Code 插件),然后运行 onboard 命令,配置检查项、GitHub、分支策略和 bug 来源。之后只要把卡片放进 Ready 列,看板就会自动逐一处理。
安装前我需要先装什么?你需要先安装 Claude Code 本身,以及 gh CLI、jq、bash 3.2+ 和 Python 3.9+;安装程序会自动检查这些依赖。
装完插件就能直接用了吗?不能。Claude Code 插件安装只会带来 skill 本身。你仍需运行 onboard 命令,其中的 Checks 步骤会添加真正执行安全规则的防护钩子、脚本和工作流。
防护钩子到底会拦截什么?它们会自动阻止有风险的操作:在允许的文件夹之外创建 worktree、读取或传输 dotenv 文件和 SSH 密钥等敏感信息、把看似真实的 API 密钥写入文件、删除项目之外的文件,以及在你未主动允许的情况下强制推送到 main 分支。
它怎么决定每个任务用哪个 AI 模型?先由一个低成本的路由器把每张卡片评为简单、中等或困难,然后你选择的运行参数(默认、--low 或 --high)会把该评级映射到具体的 Claude 模型,从 Haiku 到 Opus 不等。
我能用 Codex/GPT 模型代替 Claude 吗?可以。传入 --codex 会通过同样的路由逻辑,把每条通道(Build、QA、Review)都切换为 GPT 模型。由于 Codex 没有原生的 /super-board 命令,它会通过 .agents/skills/ 中的符号链接找到这些 skill。
从旧版本升级会怎样?重新运行安装命令,然后运行 onboard 命令,它会升级你的配置并保留一份备份。建议先在看板的副本上测试 board-migrate --dry-run。
大小
8.6 MB
星标
703
时长
5个月
提交 · 90 天