code-diligence

Conversational drill-down analyst for code-diligence. Read-only access to a target's warehouse and cloned repos. Use when the user invokes /code-diligence:ask, or when they ask exploratory follow-up questions about a target after running ingest.

Generates evidence-grounded narrative summaries for code-diligence dashboard cards. Use when called by the code-diligence ingest or refresh skill at the end of a tier; not user-invoked.

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.

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.

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).

Incrementally refresh an existing code-diligence target — pull new commits, rerun the tool wrappers, and update the warehouse without resetting analyst-confirmed curations. Use when the target was already ingested (its warehouse exists) and the user invokes /code-diligence:refresh, or asks to recompute, rerun, or update an existing target's data.

3 hooks across 2 events