lovable-testing

Run and maintain Lovable Preview test plans from agent coding environments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Lovable Preview tests synchronized with code changes is tedious: test plans drift from features, preview tokens get mishandled, and agents run full test suites when a small smoke run would suffice. This Skill standardizes how coding agents generate, run, and maintain Preview tests across Codex, Claude Code, and other Agent Skills runtimes. ## Core Features & Use Cases - Test Plan Management: Generate and sync test plans under .lovable-agent/tests/ with accurate covers: paths and last-sync commit tracking. - Scoped Test Runs: Execute the smallest affected plan set (--changed or --smoke) after implementation or deployment before offering --all. - Secure Token Handling: Store preview tokens only in the gitignored preview-token.local file, falling back to browser sessions or manual checklists when unavailable. - Workspace Migration: Migrate legacy .claude/lovable-claude/test/ workspaces with scripts/migrate-workspace.py while preserving read-compatible aliases. - Use Case: After deploying a new checkout flow, ask your agent to run the changed test plans against the live Preview app, marking any paid or destructive steps as [MANUAL]. ## Quick Start Ask your agent to run the changed Lovable Preview test plans for the features you just modified and report the results.

Frequently Asked Questions about lovable-testing

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

FAQPage Schema
How do I run Lovable Preview tests from Claude Code or Codex?

Use the lovable-testing skill to run test plans stored in `.lovable-agent/tests/`. After implementation or deployment, run the smallest affected set with `--changed` or `--smoke` before offering a full `--all` run.

How do I generate a test plan for a Lovable Preview app?

The skill generates test plans under `.lovable-agent/tests/plans/` with `covers:` paths mapping tests to source files. Keep these paths accurate and update the last-sync commit after each successful plan sync.

Where should I store my Lovable preview token?

Store the preview token only in `.lovable-agent/preview-token.local`, which must be listed in `.gitignore` and never committed. Config.json should hold only the base preview URL and token dates, never the token itself.

Can I migrate tests from the old .claude/lovable-claude/test workspace?

Yes, run `scripts/migrate-workspace.py` to migrate the legacy `.claude/lovable-claude/test/` workspace into `.lovable-agent/tests/`. The legacy path remains a read-compatible alias until you opt into cleanup.

What happens when browser access is unavailable for Preview testing?

The skill prefers a valid stored token, then a logged-in browser session, then a manual checklist. Implementation should never be blocked solely because browser access is unavailable.