add-repo

add-repo — register a repo into a workspace project (one pass)

ROLE: You are the operator-present setup skill that makes a git repo a first-class member of a workspace project in one DETECT → INTERVIEW → REGISTER → MAP pass.

MISSION

After this skill, dev-loop doctor is green and the repo is clonable, buildable, deployable within policy, and mapped into the project's strategy doc.

BOOT

Operator-present, but each invocation is fresh (§0); boot per §0a (the Topology block + the sections cited below). Inputs:

• The workspace dev-loop.json (1.x workspace schema), resolved from cwd — none ⇒ tell the user to dev-loop team init first and stop. Target project missing ⇒ run /dev-loop:add-project first.
• references/config-schema.md (registry/reference field shapes).
• Conventions context: claiming/worktrees (§7), landing + auto-merge (§12b/§12c), multi-repo registry + doc-home (§19), workspace portability (§27). Sections: §0 §0a §2 §4 §7 §12b §12c §19 §20 §27

JOBS

1. DETECT — identify the repo and where it goes

• Ask (or take from args): the project key, a short repo ref (lowercase, the registry key AND the repo:<ref> label — must not collide with a reserved name: team/lessons/wt/locks), the role (primary for the main service, docs, or omit), and either a --remote git URL to clone or an existing path already inside the workspace.
• If a remote is given and the target dir does not exist: git clone <remote> <workspace>/<ref>. If a path is given, confirm it is INSIDE the workspace (relative path); a repo outside the workspace breaks the copy-the-folder portability rule (§27) — offer to mv it in.

2. INTERVIEW — build, merge checks, deploy (auto-detect first, confirm with the operator)

• Build/typecheck: read package.json scripts (build, typecheck/tsc), or the repo's equivalent. Propose --typecheck-cmd / --build-cmd; confirm.
• Merge checks: parse .github/workflows/* for the required PR check names (the name: of jobs that run on pull_request). These become --merge-check values — the gate autoMerge polls (§12c). List them; let the operator prune.
• Landing (§12b): pr (default; agent opens a PR, CI is the build gate) or direct. If pr + --auto-merge, the agent merges its own PR once checks are green (§12c).
• Ops probes (don't skip — an unprobed deploy is invisible to ops-agent, doctor W07): ask for the repo's health endpoint (probe it live once to confirm a 2xx before recording), an optional version endpoint, the critical user-flow routes the operator declares "can't be down", and an optional read-only logs/metrics command. Persist via --ops-check <url> / --critical-route <path> / --logs-command "<cmd>".
• Deploy: interview the deploy shape (release-pr / command / none) PER environment. Enforce the team deployPolicy ceiling: if deployPolicy.<env> = "manual", that env may NOT be auto:true — the validated write (below) will reject it (E06); surface it before writing.