Skip to content
Skills Library
Programming · Testing

lovable-testing

/lovable-testing

Run and maintain Lovable Preview tests from Codex, Claude Code, or another Agent Skills runtime. Use for test-plan generation, smoke/changed/all runs, test workspace migration, preview token handling, or keeping tests synchronized with changed features.

Licence
MIT
Last repository change
18.09.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run and maintain Lovable Preview tests from Codex, Claude Code, or another Agent Skills runtime. Use for test-plan generation, smoke/changed/all runs, test workspace migration, preview token handling, or keeping tests synchronized with changed features.

Original author description

Run and maintain Lovable Preview tests from Codex, Claude Code, or another Agent Skills runtime. Use for test-plan generation, smoke/changed/all runs, test workspace migration, preview token handling, or keeping tests synchronized with changed features.

How it works

SKILL.md has no level-two headings · 30 lines, 167 words

SKILL.md preview
---
name: lovable-testing
description: >-
  Run and maintain Lovable Preview tests from Codex, Claude Code, or another Agent Skills runtime.
  Use for test-plan generation, smoke/changed/all runs, test workspace migration, preview token
  handling, or keeping tests synchronized with changed features.
---

# Lovable Preview Testing

The canonical user-project test workspace is:

```text
.lovable-agent/
├── config.json
├── context.md
├── preview-token.local       # ignored credential, never committed
└── tests/
    ├── plans/
    ├── profiles/
    └── results/
```

- Treat Preview as non-production. Mark destructive, paid, or irreversible steps `[MANUAL]`.
- Store only the base preview URL and token dates in `config.json`; store the token itself only in
  `.lovable-agent/preview-token.local`, after ensuring the path is in `.gitignore`.
- Prefer a valid stored token, then a logged-in browser session, then a manual checklist. Never block
  implementation solely because browser access is unavailable.
- After implementation or deployment, run the smallest affected plan set (`--changed` or `--smoke`)
  before offering `--all`.
- Keep `covers:` paths accurate and update the last-sync commit after a successful plan sync.
- Migrate `.claude/lovable-claude/test/` with `scripts/migrate-workspace.py`; preserve the legacy
  path as a read-compatible alias until the user opts into cleanup.

The existing `../testing/` skill and its references remain the Claude command implementation. Read
`../lovable/references/agent-config.md` for the neutral config schema and migration mapping.

Versions

The database has no other skills named lovable-testing.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 33fa1ad5cad1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86lovable-sync
    Synchronize Lovable projects with GitHub safely. Use when pulling the latest main branch, checking GitHub/Lovable drift, initializing `.lovable-agent`, migrating the legacy Claude test workspace, or committing and pushing changes for Lovable two-way sync.
  • 91lovable
    Read, create, edit, and deploy web apps and projects in Lovable. Use to turn a product brief into a working website or prototype, inspect existing project code, update pages and features, and publish changes through Lovable's official MCP server.
  • 100lovable-cloud-knowledge
    Lovable's UI knowledge fields and workspace skill files — `.lovable/*.md` repo-mirror workflow, `.agents/skills/` propagation model, Project/Workspace scope split, precedence, review criteria. TRIGGER when: authoring or reviewing changes to `.lovable/*.md` or…
  • 86lovable-project
    Provider-neutral project context for Lovable.dev repositories. Use when initializing, inspecting, or modifying a Lovable project, detecting Vite SPA versus TanStack Start, reading `.lovable-agent` configuration, or generating agent instruction shims for Codex, Claude Code, and other agents.
  • 100lovable-cloud-migration-sync
    Post-apply cleanup for Lovable-duplicated migrations: diff originals, db reset, delete, open PR. TRIGGER when: the user signals Lovable's migration apply step completed, regardless of exact wording. DO NOT TRIGGER when: all originals already deleted, or user asks about mechanics…
  • 100lovable
    Lovable (formerly GPT Engineer) is a browser-based AI app builder that turns a natural-language description into a working full-stack web app with a built-in backend, authentication, database and one-click publishing. Use when the user wants to prototype or ship a web app with…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.