From lisa
This skill should be used when comparing a project's Lisa-managed files against Lisa's source templates to identify drift. It reads the project manifest, locates source templates, generates diffs for drifted files, and offers to upstream improvements back to Lisa.
npx claudepluginhub codyswanngt/lisa --plugin lisaThis skill uses the workspace's default tool permissions.
This skill compares the current project's Lisa-managed files against Lisa's source templates to identify drift and offer to upstream improvements back to Lisa.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill compares the current project's Lisa-managed files against Lisa's source templates to identify drift and offer to upstream improvements back to Lisa.
This skill requires access to the Lisa installation directory. Either:
--add-dir ~/lisa (or your Lisa path)/lisa-review-implementation ~/lisaFirst, determine the Lisa installation directory:
--add-dir paths contain a src/core/lisa.ts file (Lisa's signature file)~/lisa, ~/workspace/lisa, ../lisaIf Lisa directory cannot be found, inform the user:
Unable to locate Lisa installation directory.
Please either:
1. Start Claude Code with: claude --add-dir /path/to/lisa
2. Run this command with the path: /lisa-review-implementation /path/to/lisa
Read the project's .lisa-manifest file to get the list of managed files.
Parse each line to extract:
strategy: The copy strategy used (copy-overwrite, copy-contents, merge, create-only)relativePath: The file path relative to project rootSkip:
# (comments)create-only strategy (these are meant to be customized)merge strategy (these are intentionally combined)For each managed file, locate its source in Lisa by checking these directories in order:
npm-package/copy-overwrite/ and npm-package/copy-contents/cdk/copy-overwrite/ and cdk/copy-contents/nestjs/copy-overwrite/ and nestjs/copy-contents/expo/copy-overwrite/ and expo/copy-contents/typescript/copy-overwrite/ and typescript/copy-contents/all/copy-overwrite/ and all/copy-contents/The FIRST match wins (most specific type takes precedence).
Detect which project types apply by checking the project for:
npm-package: package.json without "private": true AND has main, bin, exports, or filescdk: presence of cdk.json or aws-cdk in dependenciesnestjs: presence of nest-cli.json or @nestjs in dependenciesexpo: presence of app.json, eas.json, or expo in dependenciestypescript: presence of tsconfig.json or typescript in dependenciesOnly check type directories that match the project.
For each file, compare the project version against the Lisa source:
Use the Bash tool with diff to generate readable diffs:
diff -u "/path/to/lisa/source" "/path/to/project/file" || true
Create a markdown report with these sections:
# Lisa Implementation Review
**Project:** [project name from package.json]
**Lisa Source:** [lisa directory path]
**Generated:** [current date/time]
## Summary
- **Total managed files:** X
- **In sync:** X
- **Drifted:** X
- **Source not found:** X
## Drifted Files
### [relative/path/to/file]
**Source:** [lisa-type]/copy-overwrite/[path]
**Strategy:** copy-overwrite
<details>
<summary>View diff</summary>
```diff
[diff output]
Recommendation: [Brief analysis of whether this change should be upstreamed]
[Repeat for each drifted file]
These files are in the manifest but their source templates couldn't be located:
After presenting the report, ask the user which drifted files they want to copy back to Lisa.
For each file the user wants to upstream:
typescript/copy-overwrite/.github/workflows/ci.yml)Example prompt:
I found X files that have drifted from Lisa's templates.
Which files would you like to copy back to Lisa?
1. .github/workflows/ci.yml - [brief description of changes]
2. .claude/settings.json - [brief description of changes]
3. All of the above
4. None - just show me the report
Select an option (or list specific numbers):
typescript/ and all/, upstream to where it currently existscopy-contents files like .gitignore, the comparison is trickier since the project may have additional lines - highlight only if Lisa's required lines are missingUser: /lisa-review-implementation
Claude: I'll review your project's Lisa-managed files against the Lisa source templates.
[Locates Lisa directory]
[Reads manifest]
[Compares files]
[Generates report]
# Lisa Implementation Review
**Project:** my-awesome-app
**Lisa Source:** /Users/dev/lisa
**Generated:** 2026-01-18 10:30:00
## Summary
- **Total managed files:** 45
- **In sync:** 42
- **Drifted:** 3
- **Source not found:** 0
## Drifted Files
### .github/workflows/ci.yml
**Source:** typescript/copy-overwrite/.github/workflows/ci.yml
**Strategy:** copy-overwrite
[diff details]
**Recommendation:** This adds a new caching step that improves CI performance. Good candidate for upstreaming.
---
I found 3 files that have drifted. Would you like to upstream any of these changes back to Lisa?