GitHub-Project-driven autonomous pipeline. Five verbs — onboard, lint, status, run, stop — that take a Project board from empty to drained across Build → QA → Review → Done lanes (labels qa · bug · feature route each card), with graceful shutdown / resume. Use when the user says "super-board", "/super-board", "drain my GitHub project", "set up the autonomous loop", "kick off the headless build/QA pipeline", or "stop super-board".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
| Verb | Where | What it does |
|---|---|---|
super-board onboard | interactive | one-time setup wizard; writes .claude/super-board/configs/<slug>.json |
super-board lint | interactive | walks active-pipeline issues, flags vague ACs, runs pre-flight readiness |
super-board status | interactive (read-only) | snapshot of active config, column counts, in-flight workers |
super-board run | in-session (default) | the autonomous loop: waves of the super-board-wave dynamic workflow, run from this session (worker_backend: "claude-p" opts into the legacy headless runner .claude/bin/super-board-run.sh). Also the resume command — state lives on the board, not in process memory. Accepts a model-tier flag: --low (haiku/sonnet/opus ladder), default = medium (sonnet/opus/session), --high (opus for every card). `--codex [--low |
super-board stop | interactive | graceful shutdown: posts "stopped mid-flight" comments on every in-flight issue + PR, releases assignee mutexes, kills workers + dispatcher. Next super-board run resumes. |
If invoked with no verb, ask which one.
In Codex the skill is not a slash command: it is $super-board <verb>, found in .agents/skills/.
| If user says | Load |
|---|---|
super-board onboard ... | references/onboard.md |
super-board lint ... | references/lint.md |
super-board status ... | references/status.md |
super-board run --codex[=<model>] ..., or any run from a host with no Workflow tool (overrides any configured backend) | references/run-workflow.md → "Codex runs" |
super-board run ... (default — worker_backend unset or "workflow") | references/run-workflow.md (lane lifecycles still come from references/run.md) |
super-board run ... with config worker_backend: "claude-p" (legacy, explicit opt-in) | references/run.md |
super-board stop ... / "stop the run" / "pause the loop" / "kill super-board" | references/stop.md |
| "resume" / "pick up where I left off" / "restart after stop" | references/stop.md (resume = run; no separate verb) |
| Anything about Blocked exits, 🙋 needs you, or dropping a card | references/block-template.md |
| Optional learning after a successfully completed run | references/calibration.md (external installed skill; bounded receipt; explicit existing-skill edit paths) |
| Config structure questions | references/config-schema.json |
| Worker gh-call discipline / rate-limit recovery | references/rate-limit-etiquette.md (+ scripts/super-board-gh-guard.sh) |
super-board is an autonomous trader. The interactive Claude session that invokes any of the five verbs is an orchestrator, not a worker. The orchestrator:
worker_backend: "workflow" (default) → stay in-session and run the wave loop in references/run-workflow.md (launch workflow, reconcile, repeat); "claude-p" (legacy, explicit opt-in only) → nohup .claude/bin/super-board-run.sh, report PID + log path, exit. Explicit --codex overrides either backend with headless Codex waves; so does a host with no Workflow tool, or bash .claude/bin/super-board-host.sh printing codex. The orchestrator never does product work itself.claude -p (claude-p backend), workflow lane agents (workflow backend), or headless codex exec (explicit --codex).If anything goes wrong during a run, the orchestrator captures the symptom and reports back — it does not silently expand the task into a fix. See references/run.md "Orchestrator delegation contract" for the full rule.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Sync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builder lane of the super-board pipeline — takes a `Ready` GitHub Project card into its own per-issue git worktree, makes the smallest safe change test-first (TDD, `ponytail` simplest-first, official docs first for third-party APIs, upgrades and auth/billing), opens a draft PR and hands it to QA and Review through the board; it never merges — merges go through the Reviewer's merge gate. Inside `super-board run` it runs as a lane agent in the in-session wave workflow (`workflows/super-board-wave.js`, no worker cap unless `max_workers` is set); standalone headless `claude -p` dispatch is legacy opt-in. Use when the user says "Super Build", "run the build loop", "/super-build", or invokes the skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find problems in one project and file them as tickets into its super-board Backlog — the board fixes them. Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier before filing. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Super QA canonical workflow for functional bug-bash, evidence capture, and fix-ready issue filing. Crawls routes from `docs/super-qa/queue.md` with Playwright, records screenshots/logs/HARs, files product-readable issues with clear type/priority/area labels, and continues until traversal is complete or only human-gated blockers remain. Crawling is always browser-driven, but the regression test it leaves behind is written at whichever layer the defect actually lives — unit or integration in Vitest, e2e in Playwright only when the browser is the thing that broke. Use when the user says "run super-qa", "QA review", "bug bash", "verify and fix", or invokes `/super-qa`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via `ponytail:ponytail-review`). Merges only through `super-board-merge-gate.sh`, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Unattended Impeccable check → fix loop on one page or component. It reads the target's code, grills Eric (at most 10 questions, "you pick" welcome) into a per-project taste and direction file, then runs bounded rounds. Each round a fresh checker runs Impeccable critique and audit (design review and detector in separate sub-agents) and ranks typed problems, and a fresh fixer chains the matching Impeccable commands (polish last), keeps checks green or reverts, and commits. Shots cover before vs now, light and dark, 1440 and 390, plus section crops. A fresh finish reviewer grades every fix, and the loop ends in a draft PR with a Before | After table. Standalone only: started by `/ui-refine-loop <route|component>`, never by the super-board lanes. Use when the user says "ui-refine-loop", "/ui-refine-loop", "refine loop", "iterate on this page", "polish this page with impeccable", or "keep polishing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.