lisa-integration-test_skill

Overview

This skill runs an end-to-end integration test that applies Lisa templates to a downstream project and verifies the project still builds. It automatically detects failures, guides whether to fix templates upstream in Lisa or apply project-local overrides, and retries until checks pass or a retry limit is reached. Use it from within the Lisa repository directory.

How this skill works

The skill validates that it is running from the Lisa repo and that the target project is clean and already has a .lisa-manifest. It applies Lisa to the target project, inspects git to see what changed, then runs the project's typecheck, lint, and test commands using the appropriate package manager. On failure it diagnoses whether to fix Lisa templates upstream or to add project-local overrides, applies fixes, reruns checks, and repeats up to a bounded retry limit.

When to use it

• When validating that Lisa template changes do not break a downstream repository.
• Before releasing a new Lisa template version or merging template changes.
• When onboarding a project to Lisa to ensure templates integrate cleanly.
• When debugging a downstream build or lint regression after template updates.

Best practices

• Run this from the Lisa repo root (verify src/core/lisa.ts exists).
• Ensure the target project has a clean working tree and contains .lisa-manifest.
• Determine package manager by lockfile to run the correct verification commands.
• Prefer fixing Lisa templates upstream when the change is generic; use local overrides only for project-specific needs.
• Limit automated fix-and-retry cycles (stop after three attempts) and report unresolved issues.

Example use cases

• Apply a new Lisa template change and confirm downstream typechecking, linting, and tests still pass.
• Detect and fix a template regression introduced by a refactor in Lisa, then reapply to the project.
• Validate that adding a new lint rule in Lisa does not break a downstream repo, or provide a local override when necessary.
• Automate the pre-merge verification step to prevent template changes from landing that break consumers.