メニュー
Full FactHarbor quality audit — all prompts and key pipeline stages. Use when investigating analysis quality regression, before a release phase, or after major pipeline changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Keep repository documentation lean, clear, and readable. Use automatically before adding a new document, substantially expanding or rewriting Markdown/xWiki content, adding explanatory/background sections, adding FAQs/glossaries/templates, introducing repeated framing, or reviewing a documentation diff for clutter, filler, duplication, over-broad prose, stale links, or readability problems.
MUST be used automatically for any FactHarbor bugfix, regression fix, failing test/build fix, failed-validation recovery, or defect repair — BEFORE editing code. Decides whether the best fix is reverting or amending a previous change, quarantining/deleting obsolete code, or adding new code. Also use when about to add a fallback, flag, retry, helper, guard, diagnostic, or parallel mechanism — in response to a failure or proactively (even with no failing test) — or when reviewing a diff for workaround stacking / additive repair drift.
Analyze local job reports from the most recent build/commit (HEAD by default), detect quality issues, and propose AGENTS.md-compliant fixes. Scopes to HEAD by default, or to specific job URLs / job IDs / commit / input slug passed as argument. Uses RAG (static register + handoffs + machine-readable benchmark expectations, plus dynamic follow-up scans) and runs an adaptive multi-agent debate before emitting recommendations. Complements `/prompt-diagnosis` (which is narrower — prompt provenance only) by covering evidence, boundaries, verdict reasoning, and warning severity end to end.
Structured adversarial debate on any proposition. Runs an intake/structural audit first, then spawns pipeline-mirroring roles (Advocate, Challenger, Reconciler) with optional Consistency Probes and Validator. Use when a decision needs adversarial pressure before committing — root-cause attribution, architecture choices, fix selection, design tradeoffs. Other skills invoke /debate for their adversarial synthesis steps. Adapts role count and model tiers to proposition complexity.
Consolidate all documentation in Docs/WIP/. Investigates implementation status of WIP topics using helper agents when the tool supports delegation, ensures all open items are well-described and present in the backlog, updates and cleans up backlog and status files, and moves historical/completed content to the Archive. Use this skill whenever the user says "consolidate WIP", "clean up WIP", "tidy WIP docs", "audit WIP", or asks to update the backlog from WIP — even if phrased differently. Note: this skill covers Docs/WIP/ only. To clean up the entire Docs/ tree use docs-update.
Analyze debug-analyzer.log and run tests to identify pipeline issues after a change. Standard post-change check per Captain's protocol.
SOC 職業分類に基づく
| name | audit |
| description | Full FactHarbor quality audit — all prompts and key pipeline stages. Use when investigating analysis quality regression, before a release phase, or after major pipeline changes. |
| allowed-tools | Read Glob Grep Bash |
ultrathink
Perform a comprehensive quality audit of the FactHarbor CB pipeline. Focus area: $ARGUMENTS (leave blank for full audit)
Step 1 — Read all prompt files:
Read every file under apps/web/prompts/. Note each file's role in the pipeline.
Step 2 — Read key pipeline stages:
Read these files in apps/web/src/lib/analyzer/:
claim-extraction-stage.ts, research-extraction-stage.ts, boundary-clustering-stage.ts, verdict-generation-stage.ts, aggregation-stage.ts, evidence-filter.ts
Step 3 — Identify issues across 7 categories:
Step 4 — Classify each issue:
Output a structured table: ID | Category | Severity | File:Line | Description | Recommended Fix
