dx-discover-repos

dx-discover-repos

Resolve the set of repos a work item touches and emit a structured JSON array the KAI-HUB router uses to fan a worker pipeline out — one run per repo.

This skill is the multi-repo brain of the hub model. Single-repo projects never call it: their worker fires directly via its own webhook (dual-mode workers).

Inputs

Input	Source	Notes
workItemId	skill argument	the ticket being routed
trigger-comment text	.ai/run-context/trigger-comment.txt if present, else fetch from the work item	the human comment that fired the hook (after @kai-<agent>)
repo registry	$DX_REPOS_REGISTRY (default .ai/automation/registries/repos.json)	alias → metadata; see dx-hub/shared/registry-format.md

Output (StructuredOutput)

A JSON array, constrained to known registry aliases — never invent repos:

[
  { "alias": "brand-one", "repoId": "…", "adoProject": "Example Project",
    "cloneUrl": "https://…/_git/brand-one", "branch": "development",
    "reason": "explicit 'repos:' directive in trigger comment" }
]

On ambiguity or no match the skill emits a structured error object instead of an array, which the hub turns into a clarification comment on the work item:

{ "error": "ambiguous", "code": 3, "message": "project spans 2 platforms — add 'platform:' …" }
{ "error": "no-match", "code": 8, "message": "no candidate repo matched platform=… scope=… brand=…" }

The cascade

First non-empty tier wins. Tiers 0–2 are deterministic (fully testable offline); tier 3 is the LLM fallback, constrained to registry aliases.

digraph discover {
    "Start" [shape=box];
    "Tier 0: explicit repos: directive?" [shape=diamond];
    "Tier 1: simple block present?" [shape=diamond];
    "Tier 1 route ok?" [shape=diamond];
    "Tier 2: cross-repo table?" [shape=diamond];
    "Tier 3: LLM choose from registry" [shape=box];
    "Emit JSON array" [shape=doublecircle];
    "Emit structured error" [shape=doublecircle];

    "Start" -> "Tier 0: explicit repos: directive?";
    "Tier 0: explicit repos: directive?" -> "Emit JSON array" [label="non-empty"];
    "Tier 0: explicit repos: directive?" -> "Tier 1: simple block present?" [label="empty"];

    "Tier 1: simple block present?" -> "Tier 1 route ok?" [label="yes"];
    "Tier 1: simple block present?" -> "Tier 2: cross-repo table?" [label="no"];
    "Tier 1 route ok?" -> "Emit JSON array" [label="repos resolved"];
    "Tier 1 route ok?" -> "Emit structured error" [label="exit 3 / exit 8"];

    "Tier 2: cross-repo table?" -> "Emit JSON array" [label="non-empty"];
    "Tier 2: cross-repo table?" -> "Tier 3: LLM choose from registry" [label="empty"];

    "Tier 3: LLM choose from registry" -> "Emit JSON array";
}