Run affected app feature checks, inspect evidence, or maintain this project's verifier when source or accepted behavior changes.
日本語の概要は準備中です。原文の説明を表示しています。
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Starter, not executable coverage. Before saving, replace verify-app, adapt
the map to three to five real features and add project-owned scenarios/runner.
Read the installed super-qa references/project-verifier.md create/maintain/run
contract. Keep the owning project's instructions and accepted decisions.
Document exact project runner paths and commands for doctor, selected features,
explicit --all and new run-owned output directories. Name allowed targets,
installed dependencies, reset/fixture policy and owned-process cleanup. Keep
credentials out of commands and proof. Mark unavailable setup explicitly.
Read references/feature-map.json, issue ACs, diff and current source. Select
mapped IDs, state uncovered paths and additional AC checks. Resolve this skill
for the actual host before loading it. A valid map is structure, not a test pass.
Write executable steps in this order: Select, Doctor, Launch, Drive, Inspect, Proof, Cleanup. Define real assertions for each feature and relevant side effects, including which are mocked. Record HEAD/dirty state, input hashes, selected IDs, outcomes, screenshots/logs, exact rerun command and limits. Preserve failure evidence and fail if cleanup fails.
Read current source and live local behavior before editing. Distinguish stale instructions, harness gaps, product regressions and authorized product changes. Preserve accepted assertions; cite an issue/decision before changing expectations. Rerun affected features and report old/new guidance, reason and proof.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。