Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From code-diligence
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.
npx claudepluginhub aeyeops/aeo-diligence-marketplace --plugin code-diligenceHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-diligence:ingesting-target <target> [--quick | --full]<target> [--quick | --full]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:ingest <target> [--quick|--full]`.
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:ingest <target> [--quick|--full].
Resolve <target> to a settings file at ~/.claude/code-diligence-<target>.local.md. If it does not exist, tell the user to copy the template at settings/diligence.example.local.md (path relative to the plugin root) and edit it; do not proceed.
If neither --quick nor --full was passed, ask which tier and explain the trade-off in one sentence each:
Run:
uv run --directory ${CLAUDE_PLUGIN_ROOT} code-diligence ingest <settings-path> --<tier>
After the CLI exits successfully, surface from its stdout:
storage.curation_dir)If the CLI exits non-zero, surface stderr verbatim. Do not paraphrase tool errors — wrappers already log tool_failures rows for non-fatal cases.
What gets populated and in what order: references/pipeline-stages.md.
Required external binaries and the skip behavior when they're missing: references/tool-prerequisites.md.