ワンクリックで
flywheel-healthcheck
Full health check of the codebase and flywheel dependencies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Full health check of the codebase and flywheel dependencies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Check if the codebase has drifted from the implementation plan.
Deep research on an external GitHub repository to extract implementation insights.
Set up flywheel prerequisites for this project.
Start or resume the full agentic coding flywheel. Drives the complete workflow: scan → discover → plan → implement → review.
Stop the current flywheel session and reset state.
Launch a parallel swarm of agents to implement multiple beads simultaneously.
| name | flywheel-healthcheck |
| description | Full health check of the codebase and flywheel dependencies. |
Run a comprehensive health check. $ARGUMENTS
Check all systems and produce a health score.
Dependency checks (run in parallel via Bash):
br --version — bead trackerbv --version — bead visualizercurl -s --max-time 3 http://127.0.0.1:8765/health/liveness — agent-mailgit status --short — repo cleanlinessls .pi-flywheel/checkpoint.json 2>/dev/null — checkpoint statels mcp-server/dist/server.js 2>/dev/null — MCP server builtCodebase health (use Agent(Explore)):
grep -r "TODO\|FIXME\|HACK" --include="*.ts" | wc -lBead health:
br list --json — count open/closed/in-progress/deferredbv --json — check for cycles or orphaned beadsDisplay health report:
DEPENDENCIES
✅ br v1.x.x
✅ bv v1.x.x
✅ agent-mail — healthy
⚠️ MCP server not built (run: cd mcp-server && npm run build)
CODEBASE
TODOs: N
Test coverage: N% (N test files / N source files)
Git: clean / N uncommitted changes
BEADS
Open: N | In progress: N | Closed: N | Deferred: N
Graph: ✅ no cycles | ⚠️ N orphans
HEALTH SCORE: N/10