@codyswann/lisa 2.11.0 → 2.11.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +65 -14
- package/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
package/README.md
CHANGED
|
@@ -12,9 +12,9 @@ A request to fix a bug routes to a different flow than a request to build a feat
|
|
|
12
12
|
|
|
13
13
|
### Flows and Agents
|
|
14
14
|
|
|
15
|
-
A flow is a pipeline. Each step in the pipeline is an **agent** — a scoped AI with specific tools and
|
|
15
|
+
A flow is a pipeline. Each step in the pipeline is an **agent** — a scoped AI with specific tools and instructions. One agent investigates git history, another reproduces bugs, another writes code, another verifies the result.
|
|
16
16
|
|
|
17
|
-
|
|
17
|
+
Behind the scenes, agents delegate domain-specific work to reusable instruction sets that are loaded automatically when a command runs. The same logic that triages a JIRA ticket interactively is the same logic invoked by the nightly triage workflow — you don't need to know which one is running.
|
|
18
18
|
|
|
19
19
|
Flows can nest. A build flow includes a verification sub-flow, which includes a ship sub-flow. This composition keeps each flow focused while enabling complex end-to-end workflows.
|
|
20
20
|
|
|
@@ -28,13 +28,13 @@ Lisa enforces quality through layered gates:
|
|
|
28
28
|
|
|
29
29
|
### Location Agnostic
|
|
30
30
|
|
|
31
|
-
The same rules,
|
|
31
|
+
The same rules, workflows, and quality gates apply everywhere:
|
|
32
32
|
|
|
33
33
|
- On a developer's workstation running Claude Code interactively
|
|
34
34
|
- In a GitHub Action running a nightly improvement job
|
|
35
35
|
- In a CI workflow responding to a PR review comment
|
|
36
36
|
|
|
37
|
-
The
|
|
37
|
+
The orchestration adapts to context — using MCP integrations locally and REST APIs in CI — but the standards don't change.
|
|
38
38
|
|
|
39
39
|
### Template Governance
|
|
40
40
|
|
|
@@ -44,7 +44,7 @@ Lisa distributes its standards to downstream projects as templates. When a proje
|
|
|
44
44
|
- Test and coverage infrastructure
|
|
45
45
|
- CI/CD workflows
|
|
46
46
|
- Git hooks
|
|
47
|
-
- AI agent definitions
|
|
47
|
+
- AI agent definitions and project rules
|
|
48
48
|
|
|
49
49
|
Templates follow governance rules: some files are overwritten on every update (enforced standards), some are created once and left alone (project customization), and some are merged (shared defaults with project additions).
|
|
50
50
|
|
|
@@ -58,15 +58,66 @@ curl -fsSL https://claude.ai/install.sh | bash
|
|
|
58
58
|
|
|
59
59
|
## Working With Lisa
|
|
60
60
|
|
|
61
|
-
|
|
61
|
+
Lisa exposes a small set of top-level commands that map to the work lifecycle. Run them in Claude Code; everything underneath — agents, sub-flows, and the supporting libraries that power each step — happens automatically.
|
|
62
62
|
|
|
63
|
-
|
|
63
|
+
### The Lifecycle
|
|
64
64
|
|
|
65
|
-
|
|
66
|
-
- `/build` — route through the feature build flow
|
|
67
|
-
- `/improve` — route through the improvement flow
|
|
68
|
-
- `/investigate` — route through the investigation flow
|
|
69
|
-
- `/jira:triage <TICKET-ID>` — analytical triage gate: detect ambiguities, edge cases, and verification methodology
|
|
70
|
-
- `/plan:improve-tests <target>` — improve test quality by analyzing and strengthening weak or brittle tests
|
|
65
|
+
A piece of work moves through five stages. Each stage has one command.
|
|
71
66
|
|
|
72
|
-
|
|
67
|
+
| Stage | Command | What it does |
|
|
68
|
+
| --- | --- | --- |
|
|
69
|
+
| Research | `/lisa:research <problem>` | Investigates the codebase and problem space, then produces a PRD ready for planning. |
|
|
70
|
+
| Plan | `/lisa:plan <PRD>` | Decomposes a PRD into ordered work items in your tracker (JIRA, GitHub Issues, or Linear). |
|
|
71
|
+
| Implement | `/lisa:implement <ticket>` | Takes one work item from spec to shipped: assembles an agent team, runs the build, opens a PR, handles review, merges. |
|
|
72
|
+
| Verify | `/lisa:verify` | Commits, pushes, opens a PR, monitors deploy, and verifies behavior in the target environment. Folded into `/lisa:implement` but available standalone. |
|
|
73
|
+
| Debrief | `/lisa:debrief <epic>` | After shipping, mines tickets and PRs to surface edge cases, gotchas, and friction. Produces a triage doc; `/lisa:debrief:apply` persists accepted learnings. |
|
|
74
|
+
|
|
75
|
+
Most users only ever call `/lisa:research`, `/lisa:plan`, and `/lisa:implement`. The rest run automatically as sub-flows.
|
|
76
|
+
|
|
77
|
+
### Batch and Scheduled Work
|
|
78
|
+
|
|
79
|
+
| Command | What it does |
|
|
80
|
+
| --- | --- |
|
|
81
|
+
| `/lisa:intake <queue-url>` | Scans a Ready queue (Notion PRD database, JIRA project, GitHub repo, Linear team, Confluence space) and dispatches each item through the right lifecycle command. Designed as the cron target for unattended runs. |
|
|
82
|
+
|
|
83
|
+
### Maintenance and Operations
|
|
84
|
+
|
|
85
|
+
| Command | What it does |
|
|
86
|
+
| --- | --- |
|
|
87
|
+
| `/lisa:monitor [environment]` | Checks application health, logs, error rates, and performance for the named environment. |
|
|
88
|
+
| `/lisa:product-walkthrough <route>` | Walks the live product through a real browser to ground PRD or ticket reasoning in current behavior. |
|
|
89
|
+
| `/lisa:codify-verification <type> <what>` | Converts a passing manual verification into a regression test in the appropriate framework (Playwright, integration test, benchmark). Runs automatically after `/lisa:verify`. |
|
|
90
|
+
| `/lisa:review:local` | Reviews local branch changes against `main`. |
|
|
91
|
+
| `/lisa:pull-request:review <pr-url>` | Pulls down review comments on a PR and implements the valid ones. |
|
|
92
|
+
| `/lisa:security:zap-scan` | Runs an OWASP ZAP baseline scan against the local app. |
|
|
93
|
+
|
|
94
|
+
### Targeted Improvements
|
|
95
|
+
|
|
96
|
+
These commands tighten a specific quality threshold and fix every violation in one pass — useful for incremental hardening or nightly jobs.
|
|
97
|
+
|
|
98
|
+
| Command | What it does |
|
|
99
|
+
| --- | --- |
|
|
100
|
+
| `/lisa:improve:test-coverage <pct>` | Raises coverage to the target percentage by adding tests for uncovered code. |
|
|
101
|
+
| `/lisa:improve:tests <target>` | Strengthens weak, brittle, or poorly-written tests. |
|
|
102
|
+
| `/lisa:improve:code-complexity` | Lowers the cognitive-complexity threshold by 2 and fixes resulting violations. |
|
|
103
|
+
| `/lisa:improve:max-lines <n>` | Reduces the max-file-lines threshold and fixes violations. |
|
|
104
|
+
| `/lisa:improve:max-lines-per-function <n>` | Reduces the max-lines-per-function threshold and fixes violations. |
|
|
105
|
+
| `/lisa:fix:linter-error <rule> [...]` | Fixes every violation of one or more ESLint rules across the codebase. |
|
|
106
|
+
|
|
107
|
+
### Git Helpers
|
|
108
|
+
|
|
109
|
+
| Command | What it does |
|
|
110
|
+
| --- | --- |
|
|
111
|
+
| `/lisa:git:commit [hint]` | Creates conventional commits from the current changes. |
|
|
112
|
+
| `/lisa:git:submit-pr [hint]` | Pushes and opens or updates a PR. |
|
|
113
|
+
| `/lisa:git:prune` | Prunes local branches whose remotes have been deleted. |
|
|
114
|
+
|
|
115
|
+
### Talking to Lisa in Plain English
|
|
116
|
+
|
|
117
|
+
You don't have to remember any of this. Tell Claude what you want and the right command will run:
|
|
118
|
+
|
|
119
|
+
> "I have JIRA ticket PROJ-1234. Research, plan, and implement it."
|
|
120
|
+
> "Walk through the checkout flow and tell me what's broken."
|
|
121
|
+
> "Get test coverage to 90%."
|
|
122
|
+
|
|
123
|
+
> Ask Claude: "What commands are available?" for the full list at any time.
|
package/package.json
CHANGED
|
@@ -79,7 +79,7 @@
|
|
|
79
79
|
"lodash": ">=4.18.1"
|
|
80
80
|
},
|
|
81
81
|
"name": "@codyswann/lisa",
|
|
82
|
-
"version": "2.11.
|
|
82
|
+
"version": "2.11.1",
|
|
83
83
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
84
84
|
"main": "dist/index.js",
|
|
85
85
|
"exports": {
|