AeyeOps/aeo-diligence-marketplace

asking-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…

원문 언어: 영어

ingesting-target

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…

원문 언어: 영어

interpreting-tool-output

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…

원문 언어: 영어

refreshing-target

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…

원문 언어: 영어

understanding-pe-diligence-axes

Reference for the People / Product / Process taxonomy, card-to-table mappings, confidence model, and narrative-writing contract (headline-first, cite warehouse numbers, hedge on low confidence). Use when interpreting what a dashboard card measures, writing or…

원문 언어: 영어

building-dashboard

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.

원문 언어: 영어