yolo

Automate authorized Lovable backend deployments and migrations via browser or MCP with credit conservation.

20|5|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/10K-Digital/lovable-agent-skills --skill yolo-10k-digital
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: yolo
Source: https://github.com/10K-Digital/lovable-agent-skills/tree/main/plugins/lovable/skills/yolo
Command: npx skills add https://github.com/10K-Digital/lovable-agent-skills --skill yolo-10k-digital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying Supabase edge functions and database migrations to Lovable normally requires manually copying prompts into the Lovable chat, waiting for GitHub sync, and burning credits on redundant prompts. This Skill automates authorized Lovable backend deployments and main-branch publication while aggressively conserving Lovable credits. ## Core Features & Use Cases - YOLO authorization gating: Reads deploy.yolo_mode from .lovable-agent/config.json to decide when prompts, pushes, merges, and publishes can proceed without repeated confirmation, while always preserving destructive-operation and migration confirmations. - Credit-first consolidated prompts: Combines adjacent migrations and function deployments into a single exact prompt, uses browser Cloud pages for read-only inspection, and never spends prompts on status or log queries. - Multi-transport submission: Selects browser automation, the official Lovable MCP server, or manual handoff based on deploy.mode, with fallback chains and sync verification before submission. - Use Case: After pushing a commit that modifies supabase/functions/send-email/ and adds a migration, the Skill verifies GitHub sync in the Lovable UI, submits one consolidated prompt to apply the migration and deploy the function, then verifies the result through Cloud pages and direct endpoint checks. ## Quick Start Enable YOLO mode in my Lovable project config and deploy the pending edge functions and migrations from my latest push.

Frequently Asked Questions about yolo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Lovable edge function deployment after a git push?▼

Enable yolo_mode and auto_deploy in your project configuration, then push backend changes to main. The Skill detects modified files under supabase/functions/, verifies GitHub sync in the Lovable UI, and submits a consolidated deployment prompt automatically.

How do I apply Supabase migrations to Lovable without manual prompts?▼

Commit and push migration files under supabase/migrations/ to main, then trigger the apply-migration workflow. The Skill combines adjacent safe migrations into one exact prompt and submits it via browser automation or the Lovable MCP server.

Does YOLO mode bypass confirmation for destructive database operations?▼

No. YOLO mode never overrides confirmation for destructive or irreversible database work, and it honors deploy.confirm_migrations even when enabled. Explicit task restrictions and platform-enforced approvals always remain in effect.

How does the Skill avoid wasting Lovable credits?▼

It performs all local work first, uses browser Cloud pages for read-only inspection instead of chat prompts, and submits at most one consolidated prompt naming exact artifacts. It never sends follow-up prompts for logs, status, or verification.

What happens if browser automation fails during deployment?▼

The Skill falls back gracefully: it tries the next configured transport such as the Lovable MCP server, and ultimately provides the exact consolidated prompt for manual submission. Every failure message includes troubleshooting steps and never blocks the user.