lovable-sync

Synchronize Lovable projects with GitHub main branch using safe pull and push workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping a Lovable project and its GitHub repository in sync is error-prone: diverged branches, accidental secret commits, and legacy workspace layouts can break two-way sync or lose work. This Skill enforces a safe, repeatable Git workflow so GitHub main stays the source Lovable synchronizes from. ## Core Features & Use Cases - Safe pull and push: Requires a clean worktree, fetches and compares local/remote/base before pulling, and stops with a clear conflict message when branches diverge. - Secret-aware commits: Inspects diffs before pushing, keeps secrets out of commits, and restricts auto-push to the configured branch. - Legacy workspace migration: Runs scripts/migrate-workspace.py to idempotently migrate the legacy .claude/lovable-claude/test/ workspace into the shared .lovable-agent layout. - Use Case: After finishing a feature in your IDE, ask the agent to commit and push to main so Lovable picks up the changes automatically, without manually checking drift or worrying about leaking API keys. ## Quick Start Ask the agent to pull the latest main branch and push my current changes to GitHub so Lovable stays in sync.

Frequently Asked Questions about lovable-sync

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

FAQPage Schema
How do I sync a Lovable project with GitHub?

Treat GitHub main as the source Lovable synchronizes from. Read .lovable-agent/config.json for sync.branch, sync.auto_sync, and sync.auto_push settings, then pull with a clean worktree and push only on the configured branch after inspecting the diff.

How do I migrate the legacy .claude/lovable-claude/test workspace?

Run scripts/migrate-workspace.py when a project contains .claude/lovable-claude/test/. The migration is idempotent, copies non-secret test artifacts into the new layout, and keeps both token paths git-ignored.

What happens when local and remote branches diverge during a pull?

The sync stops with a clear conflict message instead of merging or discarding changes. It fetches first, compares local, remote, and base refs, and never discards user changes, leaving the worktree recoverable with manual Git commands.

Does auto-push work on branches other than main?

Auto-push is allowed only on the configured branch, normally main. Before any push, the diff is inspected to keep secrets out of commits and the intended branch is confirmed.

Do Lovable edge functions sync automatically from GitHub?

No. Lovable frontend changes sync from GitHub automatically, but edge functions and migrations may still require a Lovable deployment prompt. Use the lovable-deploy skill for that decision.