@mutmutco/kilo-plugin 3.105.5 → 3.105.6
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/skills/mmi/SKILL.md +4 -0
- package/skills/worktree/SKILL.md +19 -0
package/package.json
CHANGED
package/skills/mmi/SKILL.md
CHANGED
|
@@ -292,6 +292,10 @@ something else* paths.)
|
|
|
292
292
|
For long markdown, materialize a temporary UTF-8 body file, pass its real path with
|
|
293
293
|
`--body-file <path>`, then remove it after the write succeeds. Do not pipe multiline markdown to
|
|
294
294
|
`--body-file -` on a guarded host.
|
|
295
|
+
A title with backticks needs `--title-file` (#3381). On Windows Git Bash, a title that starts
|
|
296
|
+
with `/` (or contains an MSYS-path-shaped token) is rewritten before `mmi-cli` sees it — e.g.
|
|
297
|
+
`--title "/update …"` becomes `C:/Program Files/Git/update …`. Prefer `--title-file <path>`, or
|
|
298
|
+
prefix the create with `MSYS_NO_PATHCONV=1` (#4373).
|
|
295
299
|
The command starts bounded related-issue discovery off-path. It auto-comments only high-confidence,
|
|
296
300
|
idempotent links. To inspect candidates manually before writing anything else:
|
|
297
301
|
```bash
|
package/skills/worktree/SKILL.md
CHANGED
|
@@ -23,6 +23,11 @@ automatically).
|
|
|
23
23
|
|
|
24
24
|
The issue-ref form derives `<issue-number>-<short-slug>`, assigns the item, and moves it to In Progress.
|
|
25
25
|
|
|
26
|
+
`worktree create` also leases the tree to the **creating session** (#4328). A later `jerv-cli lane submit
|
|
27
|
+
--dir` (or any governed seat) refuses an already-held host lease and will not commandeer it. Before handing
|
|
28
|
+
the tree to a governed seat, release that lease first: discover it with `jerv-cli lease list`, then
|
|
29
|
+
`jerv-cli lease close <leaseId>`.
|
|
30
|
+
|
|
26
31
|
## Step 2 — claim + work
|
|
27
32
|
|
|
28
33
|
Work in the provisioned worktree. Exercise the change with `/stage` (a local stage is bound to the worktree that
|
|
@@ -67,6 +72,20 @@ branch refs. You do not need to `cd` out first; if removal still fails (IDE lock
|
|
|
67
72
|
sweep retries from a safe cwd. Prefer the primary checkout cwd only when you are running `worktree land`
|
|
68
73
|
manually outside `pr land`.
|
|
69
74
|
|
|
75
|
+
**No main lineage on a squashable development PR (#4365 / #4371):** never `git merge -s ours` (or otherwise
|
|
76
|
+
merge) a main-parented port commit into a development PR that will squash. Squash folds second-parent
|
|
77
|
+
trailers — including foreign `Closes #N` — into the development squash body, closes the wrong issues, and
|
|
78
|
+
trips the closing-keyword land guard. Keep the cherry-pick / main-clean source on a separate branch or ref;
|
|
79
|
+
land only development-tree changes on the development PR. To record a pushed main-clean SHA for a later
|
|
80
|
+
`/hotfix --from` without polluting squash parents, prefer a marker-only commit on the development branch
|
|
81
|
+
that references that SHA in the message — do not pull the main commit into the squashable parent list.
|
|
82
|
+
This does not weaken the `#3167` merge floor on `/hotfix` and `/release` (never squash a tagged commit;
|
|
83
|
+
alignment / roll-forward stays a true merge).
|
|
84
|
+
|
|
85
|
+
If a PR already inherited closed-issue `Closes` keywords from that anti-pattern and `pr land` / `pr merge`
|
|
86
|
+
refuses, land with `--force` only when those inherited targets are already closed — prefer preventing the
|
|
87
|
+
pollution above over relying on `--force`.
|
|
88
|
+
|
|
70
89
|
## Step 5 — record + next
|
|
71
90
|
|
|
72
91
|
Record durable decisions on the issue or PR, then check the board again:
|