@codyswann/lisa 2.333.2 → 2.333.3
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/dist/core/upstream-evidence-manifest.js +1 -1
- 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/.codex-plugin/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
- package/plugins/lisa/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
- package/plugins/lisa-agy/plugin.json +1 -1
- package/plugins/lisa-agy/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
- package/plugins/lisa-cdk/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-agy/plugin.json +1 -1
- package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-copilot/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
- package/plugins/lisa-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-cursor/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
- package/plugins/lisa-expo/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-agy/plugin.json +1 -1
- package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-expo-cursor/.claude-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-harper-fabric-agy/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-harper-fabric-cursor/.claude-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-nestjs-agy/plugin.json +1 -1
- package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-nestjs-cursor/.claude-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-openclaw-agy/plugin.json +1 -1
- package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser/.codex-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-agy/plugin.json +1 -1
- package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-phaser-cursor/.claude-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-rails-agy/plugin.json +1 -1
- package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-rails-cursor/.claude-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-typescript-agy/plugin.json +1 -1
- package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-typescript-cursor/.claude-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/lisa-wiki-agy/plugin.json +1 -1
- package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json +1 -1
- package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json +1 -1
- package/plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md +12 -3
|
@@ -434,7 +434,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
|
|
|
434
434
|
"plugins/src/base/skills/lisa-detect-tooling/scripts/commands.mjs": "e28bd61fdde4a336b56ae3395423026943a5816015719d31d04f0d5a0ab50eec",
|
|
435
435
|
"plugins/src/base/skills/lisa-detect-tooling/scripts/detect-tooling.mjs": "9d06590e6b99cce33e5fb10bd5b9e7515318133e3635368ef47162abc123bdfa",
|
|
436
436
|
"plugins/src/base/skills/lisa-doctor/SKILL.md": "fb41a1e63c5332d47a46e715aff52551f3df867033b5e4f37dfaeee30019b891",
|
|
437
|
-
"plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md": "
|
|
437
|
+
"plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md": "55de8bb44a958f5afd97deca410423b86a3c6d79bf571119304cf497c5a7a653",
|
|
438
438
|
"plugins/src/base/skills/lisa-epic-triage/SKILL.md": "d02760411249bddbd396f283191fe3e82bb7b95bf9393a19a7025dc5a57c3ab7",
|
|
439
439
|
"plugins/src/base/skills/lisa-evaluation-suite/SKILL.md": "96b5c2091ccd22a565935a7b0b917f67998881b81055ce3e4d518319472eac8b",
|
|
440
440
|
"plugins/src/base/skills/lisa-exploratory-qa/SKILL.md": "bc34dfc6418bff6eb5bc03f0c5cd98c7b6164ca3f4f80774d981f681321119b0",
|
package/package.json
CHANGED
|
@@ -115,7 +115,7 @@
|
|
|
115
115
|
"brace-expansion": ">=5.0.9"
|
|
116
116
|
},
|
|
117
117
|
"name": "@codyswann/lisa",
|
|
118
|
-
"version": "2.333.
|
|
118
|
+
"version": "2.333.3",
|
|
119
119
|
"description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
|
|
120
120
|
"main": "dist/index.js",
|
|
121
121
|
"exports": {
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.333.
|
|
3
|
+
"version": "2.333.3",
|
|
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.333.
|
|
3
|
+
"version": "2.333.3",
|
|
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"
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lisa-openclaw",
|
|
3
|
-
"version": "2.333.
|
|
3
|
+
"version": "2.333.3",
|
|
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.333.
|
|
3
|
+
"version": "2.333.3",
|
|
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.333.
|
|
3
|
+
"version": "2.333.3",
|
|
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"
|
|
@@ -14,9 +14,18 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
|
|
|
14
14
|
|
|
15
15
|
- `pr=<number|url>` — the PR to drive. Default: the PR for the current branch
|
|
16
16
|
(`gh pr view --json number,url,baseRefName,headRefName,state`).
|
|
17
|
-
- `merge_method=<merge
|
|
18
|
-
fallback. Default
|
|
19
|
-
`chore(release): X.Y.Z [skip ci]`
|
|
17
|
+
- `merge_method=<merge>` — strategy for both auto-merge and the direct-merge
|
|
18
|
+
fallback. Default and only accepted value: `merge`.
|
|
19
|
+
- **Never squash** — squashing flattens `chore(release): X.Y.Z [skip ci]`
|
|
20
|
+
commits and breaks release promotion detection.
|
|
21
|
+
- **Never rebase.** REJECT `merge_method=rebase` up front with a clear message
|
|
22
|
+
rather than accepting it and verifying it wrongly. GitHub's rebase-and-merge
|
|
23
|
+
rewrites the commits — new SHAs — and creates no merge commit, so the
|
|
24
|
+
shipped-verification in section 3 cannot succeed: `verify_commit` is the
|
|
25
|
+
pre-rebase SHA and is not an ancestor of the base branch afterwards, and the
|
|
26
|
+
merge-parent assertion has nothing to assert against. A successful merge
|
|
27
|
+
would then report as a FAILED verification and drive a false fix-forward,
|
|
28
|
+
which is worse than refusing the input. See CodySwannGT/lisa#2316.
|
|
20
29
|
- `verify_commit=<sha>` — the commit that MUST end up in the merged base (for the
|
|
21
30
|
ancestry check). Default: the PR head at the time this skill starts.
|
|
22
31
|
- `auto_merge=<true|false>` — whether this skill is allowed to merge the PR at
|