菜单
Build the Observable Framework dashboard for a code-diligence target's warehouse, honoring the privacy gate on the working-pattern card. Use when the user invokes /code-diligence:dashboard, or auto-fired by the PostToolUse hook after a warehouse write.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AeyeOps/aeo-diligence-marketplace --skill building-dashboard命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Spawn a read-only conversational analyst over a code-diligence target's warehouse and repo clones for open-ended drill-down into a finding (e.g., "why is this repo a hotspot?", "who carries bus-factor risk for X?"). Use when the user invokes /code-diligence:ask. Distinct from investigating which tool fed which warehouse column — use interpreting-tool-output for that.
Initial setup for a new code-diligence target — clone repos, walk git history, run the tool wrappers, populate the warehouse, and generate curation YAMLs. Use when the user invokes /code-diligence:ingest, or sets up code-diligence on a target for the first time (no warehouse exists yet). For already-ingested targets that need new commits picked up, use refreshing-target.
Reference for mapping raw tool output (code-maat, hercules, git-of-theseus, git-fame, git-truck, repowise) to warehouse tables, tool-specific quirks, and cross-check rules. Use when debugging warehouse mismatches, investigating why two tools report different values for the same metric, deciding which canonical source to trust, or querying a specific warehouse table to compare per-tool entries — distinct from open-ended dashboard drill-down (asker) or writing narrative copy (axes).
正在显示 SKILL.md
基于 SOC 职业分类
| name | building-dashboard |
| description | Build the Observable Framework dashboard for a code-diligence target's warehouse, honoring the privacy gate on the working-pattern card. Use when the user invokes /code-diligence:dashboard, or auto-fired by the PostToolUse hook after a warehouse write. |
| argument-hint | <target> |
| allowed-tools | Bash, Read |
The user (or the PostToolUse hook) has invoked /code-diligence:dashboard <target>.
Resolve <target> to its settings file at ~/.claude/code-diligence-<target>.local.md. If missing, tell the user and stop.
Read these fields from the settings:
storage.warehouse_path — input DuckDB warehousedashboard.output_path — directory to receive the rendered dist/heuristics.allow_working_pattern_card — privacy gate (default false); see references/privacy-gate.mdBuild the dashboard. Pass --allow-working-pattern only when the flag is true:
uv run --directory ${CLAUDE_PLUGIN_ROOT} \
python -m code_diligence.dashboard.render \
--warehouse <warehouse_path> \
--output <output_path> \
[--allow-working-pattern]
On success, tell the user the output directory and the preview command:
python -m http.server -d <output_path>
On non-zero exit, surface the stderr verbatim. The renderer fails the build when the template's npm install or observable build fails — do not silently retry.
Full renderer argument surface (curation, custom output, env vars): references/render-args.md.
Template layout and what gets copied where: references/template-layout.md.