lisa-learn

Analyze downstream project git diffs and categorize changes for upstreaming to Lisa templates.

3|3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/CodySwannGT/lisa --skill lisa-learn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lisa-learn
Source: https://github.com/CodySwannGT/lisa/tree/main/.claude/skills/lisa-learn
Command: npx skills add https://github.com/CodySwannGT/lisa --skill lisa-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and capture improvements made in downstream projects after Lisa was applied, enabling those improvements to be integrated back into Lisa's core templates.

Core Features & Use Cases

  • Analyze Git Diffs: Compares project state before and after Lisa application to pinpoint valuable changes.
  • Categorize Changes: Classifies modifications as potential upstream candidates, breakage risks, safe overrides, or neutral differences.
  • Facilitate Upstreaming: Offers to copy beneficial project changes back into Lisa's templates.
  • Use Case: After applying Lisa to a new project, you notice a more efficient way to configure ESLint. This skill helps you extract that configuration and propose it for inclusion in Lisa's main ESLint template.

Quick Start

Run this skill from the Lisa repository to analyze a downstream project's git diff after Lisa was applied.

Frequently Asked Questions about lisa-learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upstream improvements from a downstream project back to Lisa templates?

To upstream improvements to Lisa templates, run the skill from the Lisa repository to analyze a downstream project's git diff, categorize modifications, and copy beneficial changes back into core templates.

How does git diff analysis identify template improvements after applying Lisa?

Git diff analysis compares the project state before and after Lisa application to pinpoint modifications, correlate changes with the manifest, and classify them as upstream candidates, breakage risks, safe overrides, or neutral differences.

What do I need to analyze downstream project changes and upstream them to Lisa?

You need to run the skill from the Lisa repository and have a target project containing uncommitted changes from a recent Lisa run for the environment validation and diff capture to function correctly.

Can I categorize code modifications to determine if they are safe to upstream?

Yes, categorization classifies each modification as a potential upstream candidate, a breakage risk, a safe override, or a neutral difference to help determine if the changes should be integrated into Lisa templates.

How do I extract a specific configuration change and propose it for inclusion in Lisa?

After applying Lisa to a project, the skill analyzes the git diff to extract specific configurations like an optimized ESLint setup and offers to directly copy that configuration into Lisa's main templates.

Why does analyzing Lisa improvements require running from the Lisa repository?

Running from the Lisa repository is required to validate the environment, capture downstream diffs, and directly facilitate copying project improvements back into the upstream Lisa template files.