journey-deploy
Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend). Smoke-tests the deployed app — hits the live URL, invokes any deployed functions, checks auth round-trip. Writes results to docs/butterbase/04-build-log.md. Blocks journey-submit if smoke fails.
Profile →npx skills add butterbase-ai/butterbase-skills --skill journey-deploy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 0. **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. 1. **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`. 2. **Functions respond.** For each function in the
- When to use
- Preflight
- Inputs
- Procedure
- Outputs
- Anti-patterns
What does the journey-deploy skill do?
Use as the deploy-verification stage of the Butterbase journey, after journey-frontend (or after any build stage if there is no frontend). Smoke-tests the deployed app — hits the live URL, invokes any deployed functions, checks auth round-trip. Writes results to docs/butterbase/04-build-log.md. Blocks journey-submit if smoke fails.
How do I install it?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-deploy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From butterbase-ai/butterbase-skills, a repository with 532 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.