Journey Deploy

Fourth stage of the Butterbase journey that smoke-tests your deployed app before you submit it to judges. Hits your live URL with curl, invokes every HTTP function you built, walks you through an OAuth round-trip if configured, and checks function logs for errors. Writes a timestamped pass/fail line to the build log for each check and blocks progression to journey-submit if anything's broken. The anti-patterns section is spot on: a 200 from your landing page means nothing if your functions throw 500s, and judges will absolutely try to log in if you claim auth works. Solid guardrail against demo day disasters.

GitHub stars: 532
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add butterbase-ai/butterbase-skills --skill journey-deploy --agent claude-code

Installs into .claude/skills of the current project.

Files

Journey: Deploy verification

Stage 4 of the guided journey. Verify the deployed app actually works end-to-end.

When to use

Dispatched by journey when current_stage: deploy.
Directly via /butterbase-skills:journey-deploy.

Preflight

If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke butterbase-skills:journey-preflight first. Wait for it to return successfully before proceeding.

Inputs

docs/butterbase/00-state.md — for app_id, deployed_url.
docs/butterbase/02-plan.md — for the function list to smoke.
docs/butterbase/04-build-log.md — to know what shipped.

Procedure

Refresh docs. Call butterbase_docs with topic: "frontend". For end-to-end smoke patterns, also WebFetch https://docs.butterbase.ai/deploy. Skip if cache is fresh.

For each check, log a one-line result to 04-build-log.md. Halt on the first ✗ and ask the user to fix or skip.

Frontend reachable. If deployed_url is set, fetch it via Bash curl -sS -o /dev/null -w "%{http_code}" <url>. Expect 200. Log <ISO> deploy curl 200 ok or ... <code> fail.

SKILL.md on GitHub