forge-cc 0.1.11 → 0.1.12

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/forge-update.md +17 -16
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "forge-cc",
3
- "version": "0.1.11",
3
+ "version": "0.1.12",
4
4
  "description": "Pre-PR verification harness for Claude Code agents — gate runner + CLI + MCP server",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/skills/forge-update.md CHANGED
@@ -10,14 +10,14 @@ Run these commands to get version info:
10
10
 
11
11
  ```bash
12
12
  # Current installed version
13
- npm list -g forge-cc --json 2>/dev/null | node -e "const d=require('fs').readFileSync('/dev/stdin','utf8');const j=JSON.parse(d);console.log(j.dependencies?.['forge-cc']?.version||'not installed')"
13
+ forge --version
14
14
 
15
15
  # Latest available version
16
16
  npm view forge-cc version
17
17
  ```
18
18
 
19
19
  Parse both versions. If the command fails, handle gracefully:
20
- - If forge-cc is not installed globally: print "forge-cc is not installed globally. Install with: `npm install -g forge-cc`"
20
+ - If `forge` is not found: print "forge-cc is not installed globally. Install with: `npm install -g forge-cc`"
21
21
  - If npm view fails (offline): print "Could not reach npm registry. Check your internet connection."
22
22
 
23
23
  ### Step 2 — Compare and Report
@@ -42,32 +42,32 @@ If an update is available, run:
42
42
  npm install -g forge-cc@latest
43
43
  ```
44
44
 
45
+ This does two things automatically:
46
+ 1. Installs the new version globally
47
+ 2. The `postinstall` hook runs `forge setup --skills-only`, which syncs all skills to `~/.claude/commands/forge/`
48
+
45
49
  Verify the update succeeded:
46
50
 
47
51
  ```bash
48
- npm list -g forge-cc --json 2>/dev/null | node -e "const d=require('fs').readFileSync('/dev/stdin','utf8');const j=JSON.parse(d);console.log(j.dependencies?.['forge-cc']?.version||'failed')"
52
+ forge --version
49
53
  ```
50
54
 
51
- ### Step 4 — Re-sync Skills
55
+ If the version matches the latest, the update is complete. If it doesn't match, check if the user needs to restart their terminal or if there's a local `node_modules` shadowing the global install.
56
+
57
+ ### Step 4 — Verify Skills Synced
52
58
 
53
- After updating, copy the latest skills to `~/.claude/commands/forge/`:
59
+ Confirm skills were updated by listing the target directory:
54
60
 
55
61
  ```bash
56
- mkdir -p ~/.claude/commands/forge
62
+ ls ~/.claude/commands/forge/
63
+ ```
57
64
 
58
- SKILLS_DIR="$(dirname "$(which forge)")/../lib/node_modules/forge-cc/skills"
59
- if [ ! -d "$SKILLS_DIR" ]; then
60
- SKILLS_DIR="node_modules/forge-cc/skills"
61
- fi
65
+ If the directory is empty or missing, the postinstall hook may have failed silently. Run the manual fallback:
62
66
 
63
- for f in "$SKILLS_DIR"/forge-*.md; do
64
- name=$(basename "$f" | sed 's/^forge-//')
65
- cp "$f" ~/.claude/commands/forge/"$name"
66
- done
67
+ ```bash
68
+ forge setup --skills-only
67
69
  ```
68
70
 
69
- Print: "Synced skills to ~/.claude/commands/forge/"
70
-
71
71
  ### Step 5 — Post-Update Check
72
72
 
73
73
  After updating, check if the current project's forge files need refreshing:
@@ -83,6 +83,7 @@ Print final summary:
83
83
 
84
84
  **Previous:** v{old}
85
85
  **Current:** v{new}
86
+ **Skills:** Synced to ~/.claude/commands/forge/
86
87
 
87
88
  {If forge project: "Consider running `/forge:setup` (Refresh) to update project files."}
88
89
  ```