Review
Scannednpx machina-cli add skill TonyCasey/lisa/review --openclawReview Skill
Purpose
Automatically analyzes a codebase when Lisa is installed, creating a foundational memory of the project structure, technologies, and patterns. This review serves as context for all future Claude sessions.
Triggers
Use when the user says things like:
- "run review"
- "analyze this codebase"
- "scan the project"
- "what is this project about"
- "refresh codebase summary"
How to use
Automatic (during npm install)
The review runs automatically when Lisa is installed via npm install @tonycasey/lisa. It:
- Detects if the folder is a codebase
- Runs static analysis (language, framework, structure)
- Stores result as first memory
- Queues background AI enrichment
Manual commands
# Run review (or re-run with --force)
lisa review run [--force]
# Show current review
lisa review show
# Check status (done, enriched, etc.)
lisa review status
I/O contract
Static analysis output
{
"status": "ok",
"action": "run",
"result": {
"version": "1.0",
"project": { "name": "lisa", "path": "/dev/lisa", "groupId": "dev-lisa" },
"codebase": {
"language": "TypeScript",
"languages": ["TypeScript", "JavaScript"],
"framework": null,
"buildTools": ["npm", "tsc"]
},
"structure": {
"entryPoints": ["src/cli.ts", "src/index.ts"],
"mainModules": ["src/domain/", "src/infrastructure/"],
"testDirs": ["tests/"]
},
"dependencies": {
"count": 12,
"noteworthy": ["commander", "fs-extra", "@anthropic-ai/claude-code"]
},
"patterns": {
"architecture": "clean-architecture",
"testing": "node-test"
},
"metrics": {
"fileCount": 45,
"hasTests": true,
"hasDocumentation": true
}
},
"summary": "TypeScript CLI project with clean-architecture pattern..."
}
Show output
{
"status": "ok",
"action": "show",
"review": "TypeScript CLI project with clean-architecture pattern...",
"enriched": true,
"timestamp": "2026-01-11T15:30:00Z"
}
Status output
{
"status": "ok",
"action": "status",
"done": true,
"enriched": true,
"timestamp": "2026-01-11T15:30:00Z",
"groupId": "dev-lisa"
}
Memory storage
Init reviews are stored with these tags:
type:init-review- Identifies as init review memoryscope:codebase- Full codebase analysisai:enriched- Present if AI enrichment completed
Marker file
Location: .lisa/.init-review-done
Prevents re-running on subsequent installs. Delete to force re-run, or use --force flag.
Cross-model checklist
- Codex: Use explicit CLI commands; verify triggers match
- Claude: Keep output concise; shown in session-start context
- Gemini: Explicit commands; avoid model-specific tokens
Notes
- Static analysis targets <2 seconds execution
- AI enrichment runs in background (30-60 seconds)
- Logs written to
.lisa/.init-review.log - Never blocks npm install - errors are caught and logged
Source
git clone https://github.com/TonyCasey/lisa/blob/main/src/project/.lisa/skills/review/SKILL.mdView on GitHub Overview
The Review skill automatically analyzes your codebase when Lisa is installed, capturing core details like project structure, technologies, and patterns. The resulting memory acts as foundational context for all future Claude sessions, helping assistants understand the project quickly and stay aligned with its architecture.
How This Skill Works
During npm install of @tonycasey/lisa, the Review runs automatically if a codebase is detected. It performs static analysis to determine language, framework, structure, and key entry points, then stores the result as the first memory. It also queues background AI enrichment to flesh out context without blocking installation.
When to Use It
- When setting up a new project or monorepo to establish baseline memory.
- Before starting a Claude session to answer project-specific questions.
- To refresh the codebase summary after major refactors, additions, or dependency changes.
- When analyzing an unfamiliar codebase (e.g., 'analyze this codebase' or 'scan the project').
- During onboarding or handoff to new team members for quick orientation.
Quick Start
- Step 1: npm install @tonycasey/lisa
- Step 2: Allow automatic review on install, or run 'lisa review run [--force]' to trigger manually
- Step 3: Inspect results with 'lisa review show' or 'lisa review status'
Best Practices
- Ensure you are at the project root when installing Lisa so the codebase is detected.
- Trust the static analysis to run quickly (target under 2 seconds) and let enrichment occur in the background.
- Use lisa review status and lisa review show to confirm completion and enrichment.
- Keep the marker file .lisa/.init-review-done in place to avoid unnecessary reruns.
- If the project structure changes substantially, re-run with --force to refresh memory.
Example Use Cases
- Example 1: A TypeScript CLI project (e.g., a tool with src/cli.ts and src/index.ts) uses clean-architecture; Review captures language, architecture, entry points, and test directories.
- Example 2: A Node.js Express web service; Review identifies dependencies, buildTools (npm, tsc), and testing approach to seed project context.
- Example 3: A Python data-processing package; Review records language and structure to map modules and entry points for Claude.
- Example 4: A large monorepo with multiple packages; Review aggregates per-project codebase patterns and architecture for holistic context.
- Example 5: A legacy codebase undergoing refactor; run review to summarize current state before migration and guide incremental changes.