lovable-deploylisted

# `/lovable-deploy` — Lovable round-trip driver ## Usage ``` /lovable-deploy {site-slug} {prompt-source} [--auto-approve] ``` | Argument | Required | Description | |----------|----------|-------------| | `{site-slug}` | yes | Site folder name under `sites/` (e.g., `site-a`, `site-b`). Must have `Lovable project ID` field in `site-info.md`. | | `{prompt-source}` | yes | Either (a) a slug resolving to `sites/{site}/_drafts/{slug}/lovable-prompt.md`, or (b) an absolute path to any prompt file. | | `--auto-approve` | no | Opt-in. When set, skill clicks Publish → Update after build succeeds. Subject to eligibility rules — see "Auto-approve eligibility" below. | **Examples:** ``` /lovable-deploy site-a 2026-05-22-blog-quick-wins-q3 /lovable-deploy site-b services-tapas-priced-menus --auto-approve /lovable-deploy site-a /absolute/path/to/prompt.md ``` ## Why this skill exists The weekly drafter cron writes Lovable-ready prompts to `_drafts/` but cannot drive the user's local Chrome to publish them (remote sessions don't have access to local MCP servers). Manually pasting each draft into Lovable, waiting for the build, reviewing the diff, and clicking Publish takes 15-20 minutes of attention. This skill collapses that to 2-4 minutes of Claude-driven work that the user can supervise while doing other things. When Anthropic ships cross-session MCP support, this skill becomes fully autonomous (cron fires it directly). For now, the cron queues `_inbox/lovable-deploy-pending-*.md`