lisa-review-project_skill

Overview

This skill compares Lisa's source templates against a target project that already has Lisa applied to identify drift and opportunities to adopt project improvements back into Lisa. It validates that you are running from the Lisa repository, reads the target project's .lisa-manifest, detects project types, compares template files, and generates a clear report of findings. It can optionally help copy approved improvements from the project into Lisa with user confirmation.

How this skill works

The skill first confirms it is running from the Lisa repository (checks for src/core/lisa.ts) and validates the provided project path and presence of .lisa-manifest. It detects project types by inspecting package.json and key files (cdk.json, tsconfig.json, expo files, etc.), reads the manifest line-by-line, and maps each manifest entry to the most specific Lisa source template. For copy-overwrite and copy-contents files it computes diffs, categorizes drift (improvement, customization, bug fix, divergence), and produces a markdown report. If requested, it interactively copies selected project files back into the appropriate Lisa type directory with explicit user confirmation.

When to use it

• You want to see what a specific project changed after Lisa was applied.
• You need to identify template drift and decide whether to merge improvements into Lisa.
• Before releasing updates to Lisa, to capture project-driven fixes or enhancements.
• When auditing multiple projects to consolidate best practices back into Lisa.

Best practices

• Run this from the Lisa repository root to ensure correct mapping of source templates.
• Always review diffs and classifications before adopting any changes into Lisa.
• Prefer adopting changes into the most specific type directory where the source currently lives.
• Skip auto-adoption; require explicit confirmation for every file copy.
• Consider platform-specific differences (line endings, env vars) and avoid blindly adopting those.

Example use cases

• Detect a CI workflow improvement in a project and adopt the improved pipeline into Lisa's templates.
• Identify project-specific customizations that should remain local and mark them as create-only.
• Find and accept a bug fix a project made to a Lisa template.
• Generate a report for maintainers summarizing drift across managed files before a Lisa release.