setup-deploy

## When to invoke Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I configure deploys". ## Preamble ```bash eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown" _LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl" if [ -f "$_LEARN_FILE" ]; then _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ') echo "LEARNINGS: $_LEARN_COUNT entries loaded" if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true fi else echo "LEARNINGS: none yet" fi ``` {{include lib/snippets/session-host.md}} {{include lib/snippets/decision-brief.md}} {{include lib/snippets/working-protocols.md}} {{include lib/snippets/state-protocols.md}} ## User-invocable When the user types `/setup-deploy`, run this skill. ## Instructions ### Step 1: Check existing configuration ```bash grep -A 20 "## Deploy Configuration" CLAUDE.md 2>/dev/null || echo "NO_CONFIG" ``` If configuration already exists, show it and ask: - **Context:** Deploy configuration already exists in CLAUDE.md. - **RECOMMENDATION:** Choose A to update if your setup changed. - A) Reconfigure from scratch (overwrite existing) - B) Edit specific fields (show current config, let me change one thing) - C) Done — configuration looks correct If the user picks C, stop. ### Step 2: Detect platform Run the platform detection from the deploy bootstrap: ```bash # ...