thevoidforge-methodology 23.1.0 → 23.1.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/.claude/commands/void.md +23 -12
- package/package.json +1 -1
package/.claude/commands/void.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# /void — Bombadil's Forge Sync
|
|
2
2
|
|
|
3
|
+
> **Note:** This branch is a tombstone redirect. Running `/void` here upgrades your methodology to the latest from `main`. For the best experience, install the VoidForge CLI: `npm install -g thevoidforge`
|
|
4
|
+
|
|
3
5
|
## Context Setup
|
|
4
6
|
1. Read `/docs/methods/FORGE_KEEPER.md`
|
|
5
7
|
2. Read `VERSION.md` (~30 lines — current version + history)
|
|
@@ -23,18 +25,27 @@ Orient to the current state:
|
|
|
23
25
|
Fetch the latest from upstream. Two transports supported:
|
|
24
26
|
|
|
25
27
|
**Transport A (npm — v21.0+):** If `npx voidforge` is available:
|
|
26
|
-
1.
|
|
27
|
-
2.
|
|
28
|
-
|
|
29
|
-
|
|
28
|
+
1. Check: run `npx voidforge --version` to get the installed CLI version
|
|
29
|
+
2. **CLI freshness check (MANDATORY):** Run `npm view thevoidforge version` to get the latest npm version. Compare the two:
|
|
30
|
+
- If the CLI version is BEHIND npm latest → run `npm install -g thevoidforge@latest` FIRST. This is critical: old CLIs (pre-v23.1.1) compare against their own bundled methodology and will falsely report "up to date." The upgrade must happen BEFORE `npx voidforge update`.
|
|
31
|
+
- If the install fails (permissions) → try `sudo npm install -g thevoidforge@latest` or suggest the user run it manually
|
|
32
|
+
- After upgrading, verify with `npx voidforge --version` that the new version is active
|
|
33
|
+
3. Run `npx voidforge update` — now using the latest CLI, which has the full methodology including `.claude/agents/`
|
|
34
|
+
4. If no changes → "The forge burns bright! You're on the latest." → Stop
|
|
35
|
+
5. If changes applied → skip to Step 4 (npm transport handles Steps 2-3)
|
|
30
36
|
|
|
31
|
-
**Transport B (git — legacy):** If `npx voidforge` is
|
|
32
|
-
1.
|
|
33
|
-
2. If
|
|
34
|
-
3. Run `git
|
|
35
|
-
4.
|
|
36
|
-
|
|
37
|
-
-
|
|
37
|
+
**Transport B (git — legacy):** If `npx voidforge` is NOT available:
|
|
38
|
+
1. Offer to install: "Install VoidForge CLI for one-pass updates: `npm install -g thevoidforge`. Or continue with git transport (may require two passes for new file categories)."
|
|
39
|
+
2. If user declines or npm unavailable, proceed with git:
|
|
40
|
+
3. Run `git remote -v` — look for a remote pointing to `tmcleod3/voidforge`
|
|
41
|
+
4. If no VoidForge remote exists:
|
|
42
|
+
- Run `git remote add voidforge https://github.com/tmcleod3/voidforge.git`
|
|
43
|
+
- Use `voidforge` as the remote name
|
|
44
|
+
5. If a matching remote exists, use that name (could be `origin` or `voidforge`)
|
|
45
|
+
6. Run `git fetch <remote> main` — get the latest main branch
|
|
46
|
+
7. Read remote VERSION.md: `git show <remote>/main:VERSION.md`
|
|
47
|
+
8. Compare versions numerically (parse major.minor.patch as integers, not strings — "3.10.0" is newer than "3.9.0"):
|
|
48
|
+
- If current version matches or is ahead → announce "The forge burns bright! You're on the latest." → Stop
|
|
38
49
|
- If behind → continue to Step 2
|
|
39
50
|
|
|
40
51
|
## Step 1.5 — Spring Cleaning (Treebeard)
|
|
@@ -47,7 +58,7 @@ Check the **Migration Registry** in `/docs/methods/FORGE_KEEPER.md` for one-time
|
|
|
47
58
|
6. Present the cleanup plan alongside the update plan in Step 2
|
|
48
59
|
7. Apply cleanup in Step 3 alongside updates — same confirmation prompt ("all / selective / skip")
|
|
49
60
|
8. For tracked `logs/*` files, use `git rm --cached` (untrack but keep on disk)
|
|
50
|
-
9. If `package.json` has `dependencies`/`devDependencies` AND wizard/ is being kept → leave package.json alone. Only strip to minimal if wizard/ is being removed
|
|
61
|
+
9. If `package.json` has `dependencies`/`devDependencies` on scaffold/core AND wizard/ is being kept → leave package.json alone. Only strip to minimal if wizard/ is being removed
|
|
51
62
|
|
|
52
63
|
## Step 2 — Walk the Forest (Treebeard)
|
|
53
64
|
Compare every shared methodology file:
|