mcp-rancher: Command for Claude Code

/scaffold — fresh agent-ready repo bootstrap

This command runs the full greenfield bootstrap top-to-bottom in this session. The user invoking it IS the consent — proceed without any "are we doing this?" check.

Step 0 — Detect git environment

Slash commands assume nothing about the working tree. Detect first:

git rev-parse --is-inside-work-tree 2>/dev/null   # is this even a git repo?
git symbolic-ref --short HEAD 2>/dev/null         # current branch (empty = detached)
git worktree list 2>/dev/null                     # main checkout vs worktree?
git config --get remote.origin.url 2>/dev/null    # remote URL (empty = no remote)

What matters:

• Detached HEAD or git worktree: every PR's git checkout -b chore/... step will fail with "already used by worktree" or create an orphan branch. Adapt: skip the branch-creation step in each CHECKLIST and push with git push origin HEAD:<trunk> (where <trunk> is main, master, or whatever VIBE.yaml says).
• No remote: push steps no-op silently. Surface that and ask the user to add a remote, or proceed without push.
• Trunk-based development: if VIBE.yaml.workflow.branch_strategy: trunk exists, skip ALL git checkout -b steps and commit directly on the current branch.

Scaffolding a fresh dir? You'll git init later in Step 2 — none of the above applies yet.

Step 1 — Discovery (inline)

Ask only what you can't answer from context (fresh dir = ask all of Q1–Q5). Persist answers to .claude/session-context.md at the end.

Q1 — required: what's the goal of this session?

• a) Quick task / single edit — exit /scaffold, do the small thing.
• b) Just a question / chat — exit /scaffold, answer.
• c) Iterate on existing agent-collab project — read existing VIBE.yaml, skip to Step 3.
• d) Retrofit existing repo — exit /scaffold; tell user to run /retrofit.
• e) New greenfield project — continue with Q2–Q5.
• f) Other / write-in — parse free-text, propose a mode, confirm.