@codyswann/lisa 2.75.1 → 2.76.0
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/package.json +1 -1
- package/plugins/lisa/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa/commands/doctor.md +6 -0
- package/plugins/lisa/skills/doctor/SKILL.md +103 -0
- package/plugins/lisa/skills/doctor/agents/openai.yaml +4 -0
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki/.codex-plugin/plugin.json +1 -1
- package/plugins/src/base/commands/doctor.md +6 -0
- package/plugins/src/base/skills/doctor/SKILL.md +103 -0
package/package.json
CHANGED
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"lodash": ">=4.18.1"
|
|
83
83
|
},
|
|
84
84
|
"name": "@codyswann/lisa",
|
|
85
|
-
"version": "2.
|
|
85
|
+
"version": "2.76.0",
|
|
86
86
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
87
87
|
"main": "dist/index.js",
|
|
88
88
|
"exports": {
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional project/wiki coordination, then reports PASS/WARN/FAIL/SKIP results plus an overall verdict."
|
|
3
|
+
argument-hint: "[--fix=false]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Use the /lisa:doctor skill to audit whether the current repository is ready to use Lisa, report grouped PASS/WARN/FAIL/SKIP checks, and emit an overall readiness verdict. $ARGUMENTS
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: doctor
|
|
3
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only checks across project detection, Lisa config, runtime distribution surfaces, tracker/source preflight access, automation prerequisites, optional GitHub Project coordination, and optional wiki delegation, then reports PASS/WARN/FAIL/SKIP results plus an overall readiness verdict (`READY`, `READY_WITH_WARNINGS`, or `NOT_READY`)."
|
|
4
|
+
allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Doctor: $ARGUMENTS
|
|
8
|
+
|
|
9
|
+
Run a read-only Lisa readiness audit for the current repository.
|
|
10
|
+
|
|
11
|
+
## Purpose
|
|
12
|
+
|
|
13
|
+
`/lisa:doctor` is the deterministic answer to "is this repo actually ready to use Lisa?" It audits
|
|
14
|
+
the repository in grouped sections, reports each check as `PASS`, `WARN`, `FAIL`, or `SKIP`, and
|
|
15
|
+
emits one overall verdict: `READY`, `READY_WITH_WARNINGS`, or `NOT_READY`.
|
|
16
|
+
|
|
17
|
+
The command is repository-scoped. It validates only what can be observed from the current repo,
|
|
18
|
+
current machine, and current runtime. It does **not** create automations, labels, tracker items, or
|
|
19
|
+
other external state as part of the default audit path.
|
|
20
|
+
|
|
21
|
+
## Inputs
|
|
22
|
+
|
|
23
|
+
- Optional flags in `$ARGUMENTS` that narrow or tune read-only validation.
|
|
24
|
+
- The current repository root and its Lisa config files (`.lisa.config.json`,
|
|
25
|
+
`.lisa.config.local.json`) when present.
|
|
26
|
+
|
|
27
|
+
## Confirmation policy
|
|
28
|
+
|
|
29
|
+
Do **not** ask whether to proceed. Once invoked, run the read-only audit, print the grouped
|
|
30
|
+
results, emit the overall verdict, and stop.
|
|
31
|
+
|
|
32
|
+
Specifically forbidden:
|
|
33
|
+
|
|
34
|
+
- Previewing the number of checks and asking whether to continue.
|
|
35
|
+
- Offering "run a few checks first" or "dry-run vs real run" choices. This skill is already the
|
|
36
|
+
read-only path.
|
|
37
|
+
- Performing setup mutations just because a failing check discovered something missing.
|
|
38
|
+
|
|
39
|
+
The only legitimate reasons to stop early are:
|
|
40
|
+
|
|
41
|
+
- The current working directory cannot be resolved to a repository/root the audit can inspect.
|
|
42
|
+
- The runtime blocks all required local reads needed to even classify the repo.
|
|
43
|
+
|
|
44
|
+
## Audit contract
|
|
45
|
+
|
|
46
|
+
Doctor reports grouped checks in a stable, human-readable structure. The grouped sections include,
|
|
47
|
+
as applicable to the current repo:
|
|
48
|
+
|
|
49
|
+
1. **Project detection and runtime basics** — detect the project root, package/runtime surface, and
|
|
50
|
+
whether Lisa is installed where the repo expects it.
|
|
51
|
+
2. **Lisa config readiness** — read `.lisa.config.json` and `.lisa.config.local.json` using the
|
|
52
|
+
same local-overrides-global semantics defined by `config-resolution`; report missing required
|
|
53
|
+
keys, incompatible combinations, and committed-vs-local locality problems as findings rather
|
|
54
|
+
than mutating config.
|
|
55
|
+
3. **Tracker/source preflight** — perform read-only readiness checks for the configured `tracker`
|
|
56
|
+
and `source` only. If a required CLI, MCP surface, or auth context is unavailable in the current
|
|
57
|
+
runtime, report that explicitly instead of pretending the repo is ready.
|
|
58
|
+
4. **Runtime distribution surfaces** — confirm the command, skill, hook, and related distribution
|
|
59
|
+
surfaces relevant to this repo are present where Lisa expects them on the active runtime.
|
|
60
|
+
5. **Automation readiness** — inspect whether the configured queue source/tracker and scheduling
|
|
61
|
+
prerequisites are observable, but do **not** create, edit, or delete automations during doctor.
|
|
62
|
+
6. **Optional GitHub Project coordination** — when `github.projects.v2` is configured, delegate
|
|
63
|
+
the shared validation read to `github-project-v2` instead of reimplementing ad-hoc GraphQL
|
|
64
|
+
checks. Honor the `required=false` vs `required=true` semantics documented by
|
|
65
|
+
`config-resolution`: best-effort failures are `WARN`, required-mode failures are `FAIL`.
|
|
66
|
+
7. **Optional wiki delegation** — when a repo-local `wiki/` exists, either summarize the
|
|
67
|
+
specialized `lisa-wiki-doctor` verdict or explicitly report that deeper wiki checks are
|
|
68
|
+
available there. The base doctor stays narrower than full wiki migration enforcement.
|
|
69
|
+
|
|
70
|
+
If a check family is not applicable to the current repo, report `SKIP` with the reason.
|
|
71
|
+
|
|
72
|
+
## Output contract
|
|
73
|
+
|
|
74
|
+
The final report must:
|
|
75
|
+
|
|
76
|
+
- Separate observed facts from remediation advice.
|
|
77
|
+
- Print every check with one of `PASS`, `WARN`, `FAIL`, or `SKIP`.
|
|
78
|
+
- Emit exactly one overall verdict: `READY`, `READY_WITH_WARNINGS`, or `NOT_READY`.
|
|
79
|
+
- Stay read-only by default.
|
|
80
|
+
|
|
81
|
+
The verdict ladder is:
|
|
82
|
+
|
|
83
|
+
- `READY` — no `FAIL` and no `WARN`.
|
|
84
|
+
- `READY_WITH_WARNINGS` — no `FAIL`, but one or more `WARN`.
|
|
85
|
+
- `NOT_READY` — one or more `FAIL`.
|
|
86
|
+
|
|
87
|
+
## Delegation and reuse
|
|
88
|
+
|
|
89
|
+
- Reuse `config-resolution` for config and lifecycle role defaults instead of inventing a second
|
|
90
|
+
schema.
|
|
91
|
+
- Reuse the existing `github-project-v2` chokepoint for GitHub Project coordination checks instead
|
|
92
|
+
of inlining bespoke access logic.
|
|
93
|
+
- Reuse ideas from `lisa-wiki-doctor` for grouped verdict rendering where they fit, while keeping
|
|
94
|
+
the Lisa-wide doctor narrower than the wiki-specific migration/readiness workflow.
|
|
95
|
+
|
|
96
|
+
## Rules
|
|
97
|
+
|
|
98
|
+
- Never mutate repository, tracker, or automation state on the default doctor path.
|
|
99
|
+
- Never hardcode tracker/source label names outside the documented defaults plus configured
|
|
100
|
+
overrides from `config-resolution`.
|
|
101
|
+
- Never silently treat an unavailable check surface as success; report `WARN`, `FAIL`, or `SKIP`
|
|
102
|
+
with the explicit missing dependency.
|
|
103
|
+
- Never turn wiki-specific checks into a requirement for non-wiki repos.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.76.0",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.
|
|
3
|
+
"version": "2.76.0",
|
|
4
4
|
"description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Cody Swann"
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only readiness checks for config, runtime surfaces, tracker/source access, automation prerequisites, and optional project/wiki coordination, then reports PASS/WARN/FAIL/SKIP results plus an overall verdict."
|
|
3
|
+
argument-hint: "[--fix=false]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Use the /lisa:doctor skill to audit whether the current repository is ready to use Lisa, report grouped PASS/WARN/FAIL/SKIP checks, and emit an overall readiness verdict. $ARGUMENTS
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: doctor
|
|
3
|
+
description: "Audit whether the current repository is ready to use Lisa. Runs grouped read-only checks across project detection, Lisa config, runtime distribution surfaces, tracker/source preflight access, automation prerequisites, optional GitHub Project coordination, and optional wiki delegation, then reports PASS/WARN/FAIL/SKIP results plus an overall readiness verdict (`READY`, `READY_WITH_WARNINGS`, or `NOT_READY`)."
|
|
4
|
+
allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Doctor: $ARGUMENTS
|
|
8
|
+
|
|
9
|
+
Run a read-only Lisa readiness audit for the current repository.
|
|
10
|
+
|
|
11
|
+
## Purpose
|
|
12
|
+
|
|
13
|
+
`/lisa:doctor` is the deterministic answer to "is this repo actually ready to use Lisa?" It audits
|
|
14
|
+
the repository in grouped sections, reports each check as `PASS`, `WARN`, `FAIL`, or `SKIP`, and
|
|
15
|
+
emits one overall verdict: `READY`, `READY_WITH_WARNINGS`, or `NOT_READY`.
|
|
16
|
+
|
|
17
|
+
The command is repository-scoped. It validates only what can be observed from the current repo,
|
|
18
|
+
current machine, and current runtime. It does **not** create automations, labels, tracker items, or
|
|
19
|
+
other external state as part of the default audit path.
|
|
20
|
+
|
|
21
|
+
## Inputs
|
|
22
|
+
|
|
23
|
+
- Optional flags in `$ARGUMENTS` that narrow or tune read-only validation.
|
|
24
|
+
- The current repository root and its Lisa config files (`.lisa.config.json`,
|
|
25
|
+
`.lisa.config.local.json`) when present.
|
|
26
|
+
|
|
27
|
+
## Confirmation policy
|
|
28
|
+
|
|
29
|
+
Do **not** ask whether to proceed. Once invoked, run the read-only audit, print the grouped
|
|
30
|
+
results, emit the overall verdict, and stop.
|
|
31
|
+
|
|
32
|
+
Specifically forbidden:
|
|
33
|
+
|
|
34
|
+
- Previewing the number of checks and asking whether to continue.
|
|
35
|
+
- Offering "run a few checks first" or "dry-run vs real run" choices. This skill is already the
|
|
36
|
+
read-only path.
|
|
37
|
+
- Performing setup mutations just because a failing check discovered something missing.
|
|
38
|
+
|
|
39
|
+
The only legitimate reasons to stop early are:
|
|
40
|
+
|
|
41
|
+
- The current working directory cannot be resolved to a repository/root the audit can inspect.
|
|
42
|
+
- The runtime blocks all required local reads needed to even classify the repo.
|
|
43
|
+
|
|
44
|
+
## Audit contract
|
|
45
|
+
|
|
46
|
+
Doctor reports grouped checks in a stable, human-readable structure. The grouped sections include,
|
|
47
|
+
as applicable to the current repo:
|
|
48
|
+
|
|
49
|
+
1. **Project detection and runtime basics** — detect the project root, package/runtime surface, and
|
|
50
|
+
whether Lisa is installed where the repo expects it.
|
|
51
|
+
2. **Lisa config readiness** — read `.lisa.config.json` and `.lisa.config.local.json` using the
|
|
52
|
+
same local-overrides-global semantics defined by `config-resolution`; report missing required
|
|
53
|
+
keys, incompatible combinations, and committed-vs-local locality problems as findings rather
|
|
54
|
+
than mutating config.
|
|
55
|
+
3. **Tracker/source preflight** — perform read-only readiness checks for the configured `tracker`
|
|
56
|
+
and `source` only. If a required CLI, MCP surface, or auth context is unavailable in the current
|
|
57
|
+
runtime, report that explicitly instead of pretending the repo is ready.
|
|
58
|
+
4. **Runtime distribution surfaces** — confirm the command, skill, hook, and related distribution
|
|
59
|
+
surfaces relevant to this repo are present where Lisa expects them on the active runtime.
|
|
60
|
+
5. **Automation readiness** — inspect whether the configured queue source/tracker and scheduling
|
|
61
|
+
prerequisites are observable, but do **not** create, edit, or delete automations during doctor.
|
|
62
|
+
6. **Optional GitHub Project coordination** — when `github.projects.v2` is configured, delegate
|
|
63
|
+
the shared validation read to `github-project-v2` instead of reimplementing ad-hoc GraphQL
|
|
64
|
+
checks. Honor the `required=false` vs `required=true` semantics documented by
|
|
65
|
+
`config-resolution`: best-effort failures are `WARN`, required-mode failures are `FAIL`.
|
|
66
|
+
7. **Optional wiki delegation** — when a repo-local `wiki/` exists, either summarize the
|
|
67
|
+
specialized `lisa-wiki-doctor` verdict or explicitly report that deeper wiki checks are
|
|
68
|
+
available there. The base doctor stays narrower than full wiki migration enforcement.
|
|
69
|
+
|
|
70
|
+
If a check family is not applicable to the current repo, report `SKIP` with the reason.
|
|
71
|
+
|
|
72
|
+
## Output contract
|
|
73
|
+
|
|
74
|
+
The final report must:
|
|
75
|
+
|
|
76
|
+
- Separate observed facts from remediation advice.
|
|
77
|
+
- Print every check with one of `PASS`, `WARN`, `FAIL`, or `SKIP`.
|
|
78
|
+
- Emit exactly one overall verdict: `READY`, `READY_WITH_WARNINGS`, or `NOT_READY`.
|
|
79
|
+
- Stay read-only by default.
|
|
80
|
+
|
|
81
|
+
The verdict ladder is:
|
|
82
|
+
|
|
83
|
+
- `READY` — no `FAIL` and no `WARN`.
|
|
84
|
+
- `READY_WITH_WARNINGS` — no `FAIL`, but one or more `WARN`.
|
|
85
|
+
- `NOT_READY` — one or more `FAIL`.
|
|
86
|
+
|
|
87
|
+
## Delegation and reuse
|
|
88
|
+
|
|
89
|
+
- Reuse `config-resolution` for config and lifecycle role defaults instead of inventing a second
|
|
90
|
+
schema.
|
|
91
|
+
- Reuse the existing `github-project-v2` chokepoint for GitHub Project coordination checks instead
|
|
92
|
+
of inlining bespoke access logic.
|
|
93
|
+
- Reuse ideas from `lisa-wiki-doctor` for grouped verdict rendering where they fit, while keeping
|
|
94
|
+
the Lisa-wide doctor narrower than the wiki-specific migration/readiness workflow.
|
|
95
|
+
|
|
96
|
+
## Rules
|
|
97
|
+
|
|
98
|
+
- Never mutate repository, tracker, or automation state on the default doctor path.
|
|
99
|
+
- Never hardcode tracker/source label names outside the documented defaults plus configured
|
|
100
|
+
overrides from `config-resolution`.
|
|
101
|
+
- Never silently treat an unavailable check surface as success; report `WARN`, `FAIL`, or `SKIP`
|
|
102
|
+
with the explicit missing dependency.
|
|
103
|
+
- Never turn wiki-specific checks into a requirement for non-wiki repos.
|