# Automate Lovable Deployments

Lovable backend deployments can require repeated manual prompts and checks. This skill automates edge function and migration workflows with MCP or browser automation and reports verification results.

## Install

```bash
npx skillstore add 10k-digital/yolo
```

## Metadata

- Status: approved
- Slug: 10k-digital-yolo
- Skillstore revision: r1
- Version status: missing
- Tree hash: 440f0e6c27745064247ae0404082e1215a2f7daa87285cf2a13e448c4b95f08a
- Author: 10K-Digital
- GitHub username: 10K-Digital
- License: MIT
- Repository: https://github.com/10K-Digital/lovable-claude-code/tree/main/plugins/lovable/skills/yolo
- Ref: 7db9b9f06e0ab79c575b58bc48c4d8dc9849f424
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/10k-digital-yolo
- Manifest: https://skillstore.pages.dev/api/skills/10k-digital-yolo/manifest

## Capabilities

- Detects yolo mode settings in CLAUDE.md before running deployment workflows.
- Uses Lovable MCP send\_message when available and browser automation as a fallback.
- Generates deployment prompts for Supabase edge functions and migrations.
- Can trigger deployment automation after a successful git push when auto-deploy is enabled.
- Runs configured verification checks after deployment and summarizes results.
- Provides manual fallback prompts when automation fails.

## Use Cases

- Speed up backend iteration: Deploy changed edge functions from Claude after code is pushed and verify the result.
- Automate migration application: Submit migration prompts to Lovable and track success or failure with clear fallback steps.
- Standardize deployment checks: Use repeatable verification levels for logs, console errors, and endpoint behavior after deployment.

## Prompt Templates

### Enable yolo mode

```
Enable yolo mode for my Lovable project and explain what configuration you will read before deploying.
```

### Deploy an edge function

```
Use yolo mode to deploy the changed edge function and run the default verification checks.
```

### Apply migrations with verification

```
Use yolo mode to apply the new Supabase migration, then verify that the deployment completed successfully.
```

### Auto-deploy after push

```
After this git push succeeds, detect backend changes and use yolo auto-deploy only if the project configuration allows it.
```

## Limitations

- Requires Lovable MCP access or a working browser automation environment.
- Browser mode can break if the Lovable interface changes.
- Focused on edge functions and migrations, not all Lovable project operations.
- Auto-deploy behavior can affect production workflows if enabled without review.

## Best Practices

- Use MCP mode when possible because it is more stable than browser automation.
- Keep yolo testing enabled for deployments that affect production behavior.
- Review auto-deploy settings before pushing changes to main.

## Anti Patterns

- Do not enable auto-deploy for production changes that require manual approval.
- Do not rely on browser automation when Lovable login or UI state is unknown.
- Do not skip verification for migrations or edge functions with external dependencies.

## Security Audit

- Audited at: 2026-07-09T01:19:01.527\+00:00
- Summary: Static detections are mostly documentation false positives: Markdown backticks, example URLs, and example secret names are not executable code or leaked credentials. Semantic review found real operational risk because the skill can automate Lovable deployments, migration application, and external prompt submission when enabled.

## Stats

- Views: 208
- Downloads: 14
- Favorites: 0
- Popularity score: 0