Help us improve
Share bugs, ideas, or general feedback.
From code-diligence
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.
npx claudepluginhub aeyeops/aeo-diligence-marketplace --plugin code-diligenceHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-diligence:asking-diligence <target> <question><target> <question>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user has invoked `/code-diligence:ask <target> <question>`.
Applies 10 pre-set color/font themes or generates custom ones for slides, documents, reports, and HTML landing pages.
Share bugs, ideas, or general feedback.
The user has invoked /code-diligence:ask <target> <question>.
<target> to its settings file at ~/.claude/code-diligence-<target>.local.md. If missing, tell the user to follow skills/ingesting-target/SKILL.md first and stop.target_id, target_name, storage.warehouse_path, and storage.repo_clone_root. Export DILIGENCE_WAREHOUSE_PATH=<warehouse_path> for the agent's environment so the warehouse MCP picks it up.Task tool to spawn the diligence-asker agent (defined in agents/diligence-asker.md) with:
<question> verbatimtarget_id, target_name, repo_clone_rootSendMessage (do not respawn). A fresh /code-diligence:ask call always spins up a new agent so the read-only boundary stays intact.query the warehouse and read repo files, but cannot write narratives or modify the warehouse. If the user asks for a re-narration, redirect to skills/refreshing-target/SKILL.md (which calls the narrator with write access).Agent boundary details and the warehouse MCP query surface: references/asker-boundary.md.