lisa-review-implementation
Lisa Implementation Review
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.
Prerequisites
This skill requires access to the Lisa installation directory. Either:
- Start Claude Code with
--add-dir ~/lisa(or your Lisa path) - Pass the Lisa directory as an argument:
/lisa-review-implementation ~/lisa
Instructions
Step 1: Locate Lisa Directory
First, determine the Lisa installation directory:
- If an argument was provided, use that path
- Otherwise, check if any
--add-dirpaths contain asrc/core/lisa.tsfile (Lisa's signature file) - Common locations to check:
~/lisa,~/workspace/lisa,../lisa
More from codyswanngt/lisa
claude-code-action
Knowledge base for creating and configuring Claude Code Action GitHub workflows
43lisa-review-project
This skill should be used when comparing Lisa's source templates against a target project's implementation to identify drift. It validates the Lisa directory, detects project types, scans template directories, compares files, categorizes changes, and offers to adopt improvements back into Lisa. This is the inverse of lisa:review-implementation.
39lisa-integration-test
This skill should be used when integration testing Lisa against a downstream project. It applies Lisa templates, verifies the project still builds, and if anything breaks, fixes the templates upstream in Lisa and retries until the project passes all checks.
37lisa-learn
This skill should be used when analyzing a downstream project's git diff after Lisa was applied to identify improvements that should be upstreamed back to Lisa templates. It validates the environment, captures the diff, correlates changes with Lisa template directories, categorizes each change, and offers to upstream improvements.
35jsdoc-best-practices
Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interface docs, and the critical distinction between documenting "what" vs "why". Use this skill to understand the project's JSDoc ESLint rules and established patterns.
34plan-lower-code-complexity
This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations.
23