[rubambiza]

Adds the /repoman intent-dispatch skill (#107, epic #72), the
user-facing half of the entrypoint design. Delivers #73's setup-
conversation deliverable.

⚠️ Merge ordering

Merge the companion rossoctl/automation#110 first. It carries
repoman_match_name into the automation scripts/org.sh source. The
bundled org.sh copies in this PR are byte-identical to that source
(the 7-file parity contract); if this PR merges first, parity is broken
until #110 lands and agent-skills CI cannot detect the drift.

Changes

• skills/repoman/SKILL.md — the intent-dispatching skill: infers
  setup-vs-activate from ~/.repoman/ state, 5-question setup flow,
  bare-name reconciliation (6 rules), org-vs-repo detection. Asks only
  on genuine ambiguity with enumerated options.
• skills/repoman/scripts/org.sh — bundled copy (byte-identical to
  automation source), carries repoman_match_name.
• skills/automation-health-dashboard/scripts/org.sh — parity resync
  (7-file byte-identical contract).

HARD INVARIANT: the skill never writes ~/.repoman/ files directly —
every mutation goes through a repoman-setup.sh subcommand.

Assisted-By: Claude Code

[clawgenti]

The /repoman entrypoint skill: SKILL.md is clear and consistent with the automation-side spec, the program→skill-dir map is accurate (all five directories exist), and the bundled org.sh is byte-identical to the automation source as claimed. Two suggestions:

• suggestion (org.sh:226): the bundled copies include repoman_match_name, which only lands on automation main via companion PR rossoctl/automation#110 — merging this first would temporarily break the byte-identical parity contract.
• suggestion (SKILL.md:160): the Q1 default ~/repoman/repos fails validate_repos_dir's existence check on a fresh system unless the driver creates it first.

---

Reviewed by clawgenti using the github-pr-review skill

[clawgenti]

The Q1 mkdir -p note now matches the companion spec edit in rossoctl/automation#110, and the merge-ordering requirement is documented; the bundled org.sh copies remain byte-identical to the automation#110 source (verified). All checks pass. Ready for human review.

---

Reviewed by clawgenti using the github-pr-review skill

[mrsabath]

Well-constructed, documentation-heavy PR. The HARD INVARIANT framing (never write ~/.repoman/ directly; all mutations through repoman-setup.sh) is the right architectural boundary and is stated unambiguously. Every factual claim I could check against the automation source held up.

Verification performed

Claim	Result
Both bundled org.sh copies byte-identical to automation#110 source	pass — all three blobs are 0c411a9ab9c6546b542c63df6c4e682623e6fdfe
Program→skill-dir map (5 entries)	pass — all five directories exist on main
KNOWN_PROGRAMS allowlist matches SKILL.md	pass — link-health dep-bump pr-review automation-health repo-sync
All 5 named subcommands exist	pass — cmd_init_config, cmd_add_repo, cmd_enable_program, cmd_set_output, cmd_set_requirements
add-repo array-on-stdin form	pass — documented and implemented
repoman_parse_requirements output keys	pass — exact match on all four keys
Q1 mkdir -p necessity	pass — cmd_init_config calls validate_repos_dir but never creates the dir
programs: [entrypoint] not in allowlist	non-issue — free-form role tag, same as siblings' review/scanner
Frontmatter convention	pass — matches siblings
DCO sign-off, title lengths	pass — both commits signed, 35 and 44 chars

Notes on repoman_match_name (no action needed)

The two subtle bash hazards are both correctly handled and well-commented: capture-then-iterate preserves repoman_get_repos' fail-loud exit (a bare pipe would mask it as "zero matches"), and the if guard keeps the loop body's final status 0 so a trailing non-match doesn't return 1 under set -e. Whole-name match via ${line##*/} is substring-safe as claimed. bash 3.2-safe — no mapfile, no associative arrays.

Summary

The two points raised in the earlier review have since been addressed — the Q1 mkdir -p clarification landed in b267833, and merge ordering is now documented in the PR body.

Areas reviewed: Docs/Markdown, Shell (bash), cross-repo parity, commit conventions
Commits: 2, all signed-off: yes
CI status: passing (DCO, pr-title-check)

No must-fix issues — two suggestions/nits inline, neither blocking.

Blocking dependency: rossoctl/automation#110 must merge first (currently OPEN, MERGEABLE, BLOCKED on REVIEW_REQUIRED). This is a sequencing requirement, not a defect in this PR — but it is real: please do not merge this before automation#110.

[mrsabath]

suggestion — The "7-file parity contract" is asserted but unenforced anywhere. Neither repo's CI has a parity job: agent-skills runs only pr-verifier/project/self-assign, and automation's tests.yml checks its own function surface (test-lib-inventory.sh asserts the 28-function inventory of program-lib.sh), never the bundled agent-skills copies.

The PR body says "agent-skills CI cannot detect the drift" until #110 lands — but it can't detect drift after #110 lands either, in either direction. Worth tracking a real byte-comparison check; the merge-ordering requirement is currently enforced by human discipline alone.

[rubambiza]

Agreed, and you're right that it's unenforced in both directions even after automation#110 lands — the merge-ordering line in the PR body only covers the pre-#110 window. A real byte-comparison parity check is already tracked in #47 ("Add committed dashboard-copy parity test (automation vs agent-skills)"); I confirmed in a sweep today that it's still NOT DONE. I'll leave the contract documentation as-is here and let #47 carry the enforcement so this PR stays scoped to the skill. The ordering remains human-discipline-enforced until #47 lands.

[mrsabath]

nit — "The run path … is not implemented in this skill" — consider linking the follow-on issue number here so a reader lands on the tracking item rather than inferring it from epic #72.

[rubambiza]

Done in 6f7a53a. The run path is the "program invocation wiring" half of #107 (epic #72) rather than a separate tracker, so I linked both there instead of inventing a new issue number.