ワンクリックで
kanboard-doctor
Diagnose and fix kanboard parser issues — validates all workflow documents, reports errors, suggests fixes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Diagnose and fix kanboard parser issues — validates all workflow documents, reports errors, suggests fixes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Long-running iterative development loops. Run arbitrarily-long tasks without diluting model attention. Triggers: ralph, ralph loop, iterative loop, long-running task, development loop.
Full compactor reference — tool parameters, anti-patterns, sandbox languages, context budget, workflows.
Diagnostics — validate config, session DB, runtimes, and troubleshoot compactor issues.
Context management — compact session, recall history, run code, search content.
Stats display — context savings, session metrics, compactions, sandbox and recall/search counters.
Helps you use the /unipi:btw side-conversation workflow effectively. Use when you want to think in parallel, ask side questions without interrupting ongoing work, or inject a side thread back into the main agent.
| name | kanboard-doctor |
| description | Diagnose and fix kanboard parser issues — validates all workflow documents, reports errors, suggests fixes. |
Diagnose parser issues across all workflow documents. Non-destructive — only suggests fixes, asks user to confirm.
Execute each parser against its document type directory:
@pi-unipi/kanboardregistry.parseAll(".unipi/docs") to parse all documentsParsedDoc results including their warnings arraysGroup warnings and errors by file with line numbers:
ParsedDoc with warnings.length > 0:
filePathShow a structured error report:
📋 Kanboard Doctor Report
Files scanned: N
Files with issues: M
📄 .unipi/docs/specs/example.md
⚠ Line 15: Empty checkbox text
⚠ Line 23: Malformed checkbox (missing bracket)
📄 .unipi/docs/plans/old-plan.md
⚠ Line 5: Empty task name after status
For each issue, suggest a fix and ask user to confirm:
Non-destructive rules:
After each fix, re-run the parser on the modified file:
After all fixes, run full registry.parseAll() to confirm clean state.