gm-cc 2.0.104 → 2.0.105

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.
@@ -1,10 +1,10 @@
1
1
  {
2
- "name": "gm-cc",
2
+ "name": "gm",
3
3
  "owner": {
4
4
  "name": "AnEntrypoint"
5
5
  },
6
6
  "description": "State machine agent with hooks, skills, and automated git enforcement",
7
- "version": "2.0.104",
7
+ "version": "2.0.105",
8
8
  "metadata": {
9
9
  "description": "State machine agent with hooks, skills, and automated git enforcement"
10
10
  },
package/README.md CHANGED
@@ -22,7 +22,8 @@ This installation method is best for:
22
22
  For development or project-specific customization, install gm-cc directly into your project:
23
23
 
24
24
  ```bash
25
- bun x gm-cc@latest
25
+ cd /path/to/your/project
26
+ npm install gm-cc && npx gm install
26
27
  ```
27
28
 
28
29
  This installation method is ideal when you need to:
@@ -31,9 +32,29 @@ This installation method is ideal when you need to:
31
32
  - Use the latest development version
32
33
  - Configure platform-specific behavior per project
33
34
 
35
+ #### Installation Command Breakdown
36
+
37
+ The `npm install gm-cc && npx gm install` command performs two steps:
38
+
39
+ 1. **`npm install gm-cc`** - Downloads the gm-cc package and stores it in your project's `node_modules/` directory
40
+ 2. **`npx gm install`** - Runs the gm installer that copies configuration files into your Claude Code plugin directory
41
+
42
+ **Expected output:**
43
+ ```
44
+ $ npm install gm-cc
45
+ added 1 package in 1.2s
46
+
47
+ $ npx gm install
48
+ Installing gm-cc...
49
+ ✓ Created .claude/ directory
50
+ ✓ Copied agents/gm.md
51
+ ✓ Copied hooks to .claude/hooks/
52
+ ✓ Created .mcp.json for MCP integration
53
+ ```
54
+
34
55
  #### Installed File Structure (Project-Specific)
35
56
 
36
- After running `bun x gm-cc@latest`, your project will have:
57
+ After running `npx gm install`, your project will have:
37
58
 
38
59
  ```
39
60
  .claude/
@@ -50,32 +71,6 @@ After running `bun x gm-cc@latest`, your project will have:
50
71
 
51
72
  Each hook runs automatically at the appropriate session event. No manual trigger needed.
52
73
 
53
- ### Project Provisioning (Explicit Installation)
54
-
55
- To explicitly add all gm-cc hooks, agents, and skills to an existing project:
56
-
57
- ```bash
58
- bun x gm-cc@latest -- -p
59
- ```
60
-
61
- Or with a global installation:
62
-
63
- ```bash
64
- gm-cc -p
65
- ```
66
-
67
- This creates a project-local `.claude/settings.json` that configures hooks to use `${CLAUDE_PROJECT_DIR}` for project-specific environments. Useful for:
68
- - Explicitly provisioning gm-cc to an existing project
69
- - Overriding global plugin settings for a specific project
70
- - Team workflows requiring consistent project-level configuration
71
-
72
- The `-p` flag copies:
73
- - All hooks to `.claude/hooks/`
74
- - All agents to `.claude/agents/`
75
- - All skills to `.claude/skills/`
76
- - MCP configuration to `.claude/.mcp.json`
77
- - Project-specific hook settings to `.claude/settings.json`
78
-
79
74
  ## File Installation (Manual Setup)
80
75
 
81
76
  If you prefer manual file management, clone the repository and copy files directly:
@@ -156,8 +151,16 @@ npm install -g gm-cc@latest
156
151
  ### Project-Specific Installation
157
152
 
158
153
  ```bash
154
+ # Update the package
155
+ npm update gm-cc
156
+
159
157
  # Re-run the installer to update .claude/ directory
160
- bun x gm-cc@latest
158
+ npx gm install
159
+
160
+ # Or manually copy updated files
161
+ cp -r node_modules/gm-cc/agents/* .claude/agents/
162
+ cp -r node_modules/gm-cc/hooks/* .claude/hooks/
163
+ cp node_modules/gm-cc/.mcp.json .claude/.mcp.json
161
164
  ```
162
165
 
163
166
  ## Features