@grimoire-cc/cli 0.13.2 → 0.13.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@grimoire-cc/cli",
3
- "version": "0.13.2",
3
+ "version": "0.13.3",
4
4
  "description": "CLI tool for installing Grimoire agent and skill packs",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -58,19 +58,24 @@
58
58
  {
59
59
  "name": "grimoire.conventional-commit",
60
60
  "path": "skills/grimoire.conventional-commit",
61
- "description": "Generate git commits following Conventional Commits 1.0.0. Use for /conventional-commit, git commit, or when committing changes.",
62
- "version": "1.0.0",
61
+ "description": "Generate git commits following Conventional Commits 1.0.0. Use for /conventional-commit, git commit, or when committing changes. Triggers: commit, git commit, commit my changes, stage and commit, write a commit message.",
62
+ "version": "1.1.0",
63
63
  "triggers": {
64
64
  "keywords": [
65
65
  "conventional-commit",
66
- "git-commit"
66
+ "git-commit",
67
+ "commit",
68
+ "git commit"
67
69
  ],
68
70
  "file_extensions": [],
69
71
  "patterns": [
70
72
  "commit.*change",
71
73
  "create.*commit",
72
74
  "make.*commit",
73
- "conventional.*commit"
75
+ "conventional.*commit",
76
+ "commit.*my",
77
+ "stage.*commit",
78
+ "write.*commit"
74
79
  ],
75
80
  "file_paths": []
76
81
  }
@@ -1,9 +1,9 @@
1
1
  ---
2
2
  name: grimoire.conventional-commit
3
- description: "Generate git commits following Conventional Commits 1.0.0. Use for /conventional-commit, git commit, or when committing changes."
3
+ description: "Generate git commits following Conventional Commits 1.0.0. Use for /conventional-commit, git commit, or when committing changes. Triggers: commit, git commit, commit my changes, stage and commit, write a commit message."
4
4
  user-invokable: true
5
5
  disable-model-invocation: false
6
- version: 1.0.0
6
+ version: 1.1.0
7
7
  ---
8
8
 
9
9
  # Git Commit Generator
@@ -35,11 +35,18 @@ Generate git commit messages following the [Conventional Commits 1.0.0](https://
35
35
  | `ci` | CI configuration files and scripts |
36
36
  | `chore` | Other changes that don't modify src or test files |
37
37
 
38
+ ## Scope
39
+
40
+ - Use lowercase kebab-case: `auth`, `csv-import`, `api`
41
+ - Scope = the module, component, or file area affected
42
+ - Omit scope when the change is truly global
43
+
38
44
  ## Breaking Changes
39
45
 
40
- For breaking changes, either:
46
+ For breaking changes, use either or both:
41
47
 
42
- - Add `BREAKING CHANGE:` footer in body
48
+ - Append `!` after type/scope: `feat(api)!: change response format`
49
+ - Add `BREAKING CHANGE: <description>` footer in body
43
50
 
44
51
  Breaking changes correlate with MAJOR in SemVer.
45
52
 
@@ -73,7 +80,9 @@ When user invokes /commit:
73
80
  git commit -m "$(cat <<'EOF'
74
81
  type(scope): description
75
82
 
76
- - bullet points explaining what and why
83
+ Optional short sentence: business value this commit adds.
84
+
85
+ - bullet points for technical details / implementation notes
77
86
  - one point per logical change
78
87
  EOF
79
88
  )"
@@ -103,11 +112,12 @@ Only document changes with semantic meaning or technical impact. For pure format
103
112
  - No period at end of description
104
113
  - Keep description under 72 characters
105
114
  - Scope is optional but recommended for larger codebases
106
- - Body should explain "what" and "why", not "how"
115
+ - Body structure: optional one-sentence business value paragraph, then optional bullet points for technical details
107
116
  - Use bullet points in body when listing multiple changes — not prose paragraphs
117
+ - Omit business value sentence if there is no obvious user-facing or product impact
108
118
  - Be concise—avoid redundant or verbose language
109
119
  - **Never** use `--no-verify` unless explicitly requested
110
- - **Never** amend commits that have been pushed to remote
120
+ - **Never** amend commits that have been pushed to remote — amending local unpushed commits is fine
111
121
  - **Never** include Co-Authored-By footers in commit messages
112
122
 
113
123
  ## Examples
@@ -118,10 +128,17 @@ Only document changes with semantic meaning or technical impact. For pure format
118
128
  feat: add health check endpoint
119
129
  ```
120
130
 
121
- **Feature with scope:**
131
+ **Feature with scope and business value:**
122
132
 
123
133
  ```plain
124
134
  feat(api): add CSV enrichment endpoint
135
+
136
+ Enables bulk data enrichment without manual entry, reducing processing
137
+ time for large datasets.
138
+
139
+ - implements POST /api/v1/enrich/csv
140
+ - validates file size limit (10MB) and column schema
141
+ - returns enriched rows as streamed JSON
125
142
  ```
126
143
 
127
144
  **Fix with body:**