@smartsoft001/pro-claude-plugins 0.10.0 → 0.11.0
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/plugins/flow/.claude-plugin/plugin.json +1 -1
- package/plugins/flow/skills/commit/SKILL.md +20 -4
- package/plugins/flow-external/.claude-plugin/plugin.json +1 -1
- package/plugins/flow-external/skills/commit/SKILL.md +21 -3
- package/plugins/flow-legacy/.claude-plugin/plugin.json +1 -1
- package/plugins/flow-legacy/skills/commit/SKILL.md +20 -4
- package/plugins/smart-pro/.claude-plugin/plugin.json +1 -1
package/package.json
CHANGED
|
@@ -23,11 +23,27 @@ Create a conventional commit message based on Linear task and staged changes.
|
|
|
23
23
|
|
|
24
24
|
```
|
|
25
25
|
/commit [linearTaskId]
|
|
26
|
+
/commit [linearTaskId] --auto # Non-interactive mode for fully autonomous runs
|
|
26
27
|
```
|
|
27
28
|
|
|
28
29
|
## Parameters
|
|
29
30
|
|
|
30
31
|
- `linearTaskId` - Linear task ID (e.g., ENG-123)
|
|
32
|
+
- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts and the message-approval step. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
|
|
33
|
+
|
|
34
|
+
## Auto Mode (`--auto`)
|
|
35
|
+
|
|
36
|
+
**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
|
|
37
|
+
|
|
38
|
+
| Default behavior | `--auto` override |
|
|
39
|
+
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
40
|
+
| Analyze only staged changes; if nothing staged, warn and don't commit | If nothing is staged but the working tree has task-related modifications, STAGE THEM AUTOMATICALLY (`git add -A`, excluding obvious non-source artifacts — loose `*.png` in the repo root, `.playwright-mcp/`, `docs/mockups/`, `.benchmark-test/`, `.claude/settings.json`) and continue. Never ask "would you like me to stage" |
|
|
41
|
+
| Completeness prompt (Step 2.5 `AskUserQuestion`) | Skip the prompt; commit the current changes and note any suspected gaps in the commit body |
|
|
42
|
+
| Show message to user for approval before committing | Skip the approval; create the commit immediately with the generated message |
|
|
43
|
+
| Any other `AskUserQuestion` | Use the option marked **(Recommended)**; if none, pick the safest option and continue |
|
|
44
|
+
| Nothing to commit at all | If an existing commit already references this task (e.g. `/impl` committed the work itself), exit cleanly with a one-line statement naming that commit. Otherwise exit cleanly stating there was nothing to commit. No question either way |
|
|
45
|
+
|
|
46
|
+
**Hard requirement in `--auto`**: the run MUST end in exactly one of two states — a created commit, or an explicit one-line clean-exit statement that nothing needed committing. Ending the run with a question is a skill failure (in one-shot `--print` execution nobody can answer, the commit is silently lost, and the caller has to fall back to an emergency commit).
|
|
31
47
|
|
|
32
48
|
## Execution Checklist
|
|
33
49
|
|
|
@@ -35,10 +51,10 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
35
51
|
|
|
36
52
|
- [ ] **1. Fetch Linear task** — get title, description, labels/type from MCP Linear server
|
|
37
53
|
- [ ] **2. Analyze staged changes** — run `git diff --cached` to understand scope
|
|
38
|
-
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop
|
|
54
|
+
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop (in `--auto`: no prompt — continue and note gaps in the body)
|
|
39
55
|
- [ ] **4. Read commitlint config** — read `commitlint.config.js` for valid scopes and format
|
|
40
56
|
- [ ] **5. Generate commit message** — draft `<type>(<scope>): <subject>` with body and `Refs: <linearTaskId>`
|
|
41
|
-
- [ ] **6. Show message to user** — present commit message for approval before proceeding
|
|
57
|
+
- [ ] **6. Show message to user** — present commit message for approval before proceeding (skipped in `--auto`: commit immediately)
|
|
42
58
|
- [ ] **7. MANDATORY: Pre-commit preparation** — run `nvm use 24` then `npm run format`, stage any formatting changes
|
|
43
59
|
- [ ] **8. Create commit** — execute `git commit` with the approved message
|
|
44
60
|
- [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
|
|
@@ -208,7 +224,7 @@ After the commit is created, perform an optional parallelization analysis:
|
|
|
208
224
|
3. Select scope based on the primary area of code changes
|
|
209
225
|
4. If task type is unclear, analyze the code changes to determine type
|
|
210
226
|
5. Always include the Linear task reference in the footer
|
|
211
|
-
6. If there are no staged changes, warn the user and don't create commit
|
|
227
|
+
6. If there are no staged changes, warn the user and don't create commit (default mode only; in `--auto` stage task-related working-tree changes automatically per Auto Mode and proceed)
|
|
212
228
|
7. After a successful commit, run the optional parallelization analysis (Step 6) to surface optimization opportunities from the orchestration plan. Recurring patterns are filed as Linear issues automatically via `linear-suggestion` skill
|
|
213
229
|
|
|
214
230
|
### Example
|
|
@@ -256,4 +272,4 @@ If no orchestration plan is found in Linear comments, this step is silently skip
|
|
|
256
272
|
|
|
257
273
|
---
|
|
258
274
|
|
|
259
|
-
**Important**: Before committing, show the generated commit message to the user for approval.
|
|
275
|
+
**Important**: Before committing, show the generated commit message to the user for approval. In `--auto` mode skip the approval entirely — commit immediately and never end the run with a question (see Auto Mode).
|
|
@@ -19,20 +19,36 @@ Create a conventional commit message based on Linear task and staged changes.
|
|
|
19
19
|
|
|
20
20
|
```
|
|
21
21
|
/commit [linearTaskId]
|
|
22
|
+
/commit [linearTaskId] --auto # Non-interactive mode for fully autonomous runs
|
|
22
23
|
```
|
|
23
24
|
|
|
24
25
|
## Parameters
|
|
25
26
|
|
|
26
27
|
- `linearTaskId` - Linear task ID (e.g., FRA-123)
|
|
28
|
+
- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts and the message-approval step. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
|
|
29
|
+
|
|
30
|
+
## Auto Mode (`--auto`)
|
|
31
|
+
|
|
32
|
+
**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
|
|
33
|
+
|
|
34
|
+
| Default behavior | `--auto` override |
|
|
35
|
+
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
36
|
+
| Analyze only staged changes; if nothing staged, warn and don't commit | If nothing is staged but the working tree has task-related modifications, STAGE THEM AUTOMATICALLY (`git add -A`, excluding obvious non-source artifacts — loose `*.png` in the repo root, `.playwright-mcp/`, `docs/mockups/`, `.benchmark-test/`, `.claude/settings.json`) and continue. Never ask "would you like me to stage" |
|
|
37
|
+
| Completeness prompt (`AskUserQuestion`) | Skip the prompt; commit the current changes and note any suspected gaps in the commit body |
|
|
38
|
+
| Show message to user for approval before committing | Skip the approval; create the commit immediately with the generated message |
|
|
39
|
+
| Any other `AskUserQuestion` | Use the option marked **(Recommended)**; if none, pick the safest option and continue |
|
|
40
|
+
| Nothing to commit at all | If an existing commit already references this task (e.g. `/impl` committed the work itself), exit cleanly with a one-line statement naming that commit. Otherwise exit cleanly stating there was nothing to commit. No question either way |
|
|
41
|
+
|
|
42
|
+
**Hard requirement in `--auto`**: the run MUST end in exactly one of two states — a created commit, or an explicit one-line clean-exit statement that nothing needed committing. Ending the run with a question is a skill failure (in one-shot `--print` execution nobody can answer, the commit is silently lost, and the caller has to fall back to an emergency commit).
|
|
27
43
|
|
|
28
44
|
## Execution Checklist
|
|
29
45
|
|
|
30
46
|
- [ ] **1. Fetch Linear task** — get title, description, labels/type from MCP Linear server
|
|
31
47
|
- [ ] **2. Analyze staged changes** — run `git diff --cached` to understand scope
|
|
32
|
-
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop
|
|
48
|
+
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop (in `--auto`: no prompt — continue and note gaps in the body)
|
|
33
49
|
- [ ] **4. Determine commit type and scope** — based on changes and task type
|
|
34
50
|
- [ ] **5. Generate commit message** — draft `<type>(<scope>): <subject>` with body and `Refs: <linearTaskId>`
|
|
35
|
-
- [ ] **6. Show message to user** — present commit message for approval before proceeding
|
|
51
|
+
- [ ] **6. Show message to user** — present commit message for approval before proceeding (skipped in `--auto`: commit immediately)
|
|
36
52
|
- [ ] **7. Create commit** — execute `git commit` with the approved message
|
|
37
53
|
|
|
38
54
|
## Commit Message Format
|
|
@@ -93,6 +109,8 @@ Refs: FRA-548
|
|
|
93
109
|
|
|
94
110
|
### No Staged Changes
|
|
95
111
|
|
|
112
|
+
Default mode only — in `--auto` do NOT print this and do NOT stop: stage task-related working-tree changes automatically and continue (see Auto Mode).
|
|
113
|
+
|
|
96
114
|
```markdown
|
|
97
115
|
## No staged changes
|
|
98
116
|
|
|
@@ -108,7 +126,7 @@ If linearTaskId is not provided or task not found:
|
|
|
108
126
|
|
|
109
127
|
## Guidelines
|
|
110
128
|
|
|
111
|
-
1. **Always show commit message for approval** before creating the commit
|
|
129
|
+
1. **Always show commit message for approval** before creating the commit (default mode; in `--auto` skip the approval and commit immediately — see Auto Mode)
|
|
112
130
|
2. **Use Polish branch naming** if branch follows FRA-XXX pattern
|
|
113
131
|
3. **Include Refs:** with Linear task ID when available
|
|
114
132
|
4. **Keep subject line under 72 characters**
|
|
@@ -23,11 +23,27 @@ Create a conventional commit message based on Linear task and staged changes.
|
|
|
23
23
|
|
|
24
24
|
```
|
|
25
25
|
/commit [linearTaskId]
|
|
26
|
+
/commit [linearTaskId] --auto # Non-interactive mode for fully autonomous runs
|
|
26
27
|
```
|
|
27
28
|
|
|
28
29
|
## Parameters
|
|
29
30
|
|
|
30
31
|
- `linearTaskId` - Linear task ID (e.g., ENG-123)
|
|
32
|
+
- `--auto` - Non-interactive mode: skip ALL `AskUserQuestion` prompts and the message-approval step. Treat any of `--auto`, `--ci`, `--non-interactive` as equivalent.
|
|
33
|
+
|
|
34
|
+
## Auto Mode (`--auto`)
|
|
35
|
+
|
|
36
|
+
**When `--auto` is set, the skill MUST run end-to-end without any human-in-the-loop prompts.** Apply these overrides:
|
|
37
|
+
|
|
38
|
+
| Default behavior | `--auto` override |
|
|
39
|
+
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
40
|
+
| Analyze only staged changes; if nothing staged, warn and don't commit | If nothing is staged but the working tree has task-related modifications, STAGE THEM AUTOMATICALLY (`git add -A`, excluding obvious non-source artifacts — loose `*.png` in the repo root, `.playwright-mcp/`, `docs/mockups/`, `.benchmark-test/`, `.claude/settings.json`) and continue. Never ask "would you like me to stage" |
|
|
41
|
+
| Completeness prompt (`AskUserQuestion`) | Skip the prompt; commit the current changes and note any suspected gaps in the commit body |
|
|
42
|
+
| Show message to user for approval before committing | Skip the approval; create the commit immediately with the generated message |
|
|
43
|
+
| Any other `AskUserQuestion` | Use the option marked **(Recommended)**; if none, pick the safest option and continue |
|
|
44
|
+
| Nothing to commit at all | If an existing commit already references this task (e.g. `/impl` committed the work itself), exit cleanly with a one-line statement naming that commit. Otherwise exit cleanly stating there was nothing to commit. No question either way |
|
|
45
|
+
|
|
46
|
+
**Hard requirement in `--auto`**: the run MUST end in exactly one of two states — a created commit, or an explicit one-line clean-exit statement that nothing needed committing. Ending the run with a question is a skill failure (in one-shot `--print` execution nobody can answer, the commit is silently lost, and the caller has to fall back to an emergency commit).
|
|
31
47
|
|
|
32
48
|
## Execution Checklist
|
|
33
49
|
|
|
@@ -35,10 +51,10 @@ Execute each step in order. Do not skip any step marked as MANDATORY.
|
|
|
35
51
|
|
|
36
52
|
- [ ] **1. Fetch Linear task** — get title, description, labels/type from MCP Linear server
|
|
37
53
|
- [ ] **2. Analyze staged changes** — run `git diff --cached` to understand scope
|
|
38
|
-
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop
|
|
54
|
+
- [ ] **3. Verify completeness** — compare task requirements with staged changes; if incomplete, ask user whether to continue or stop (in `--auto`: no prompt — continue and note gaps in the body)
|
|
39
55
|
- [ ] **4. Read commitlint config** — read `commitlint.config.js` for valid scopes and format
|
|
40
56
|
- [ ] **5. Generate commit message** — draft `<type>(<scope>): <subject>` with body and `Refs: <linearTaskId>`
|
|
41
|
-
- [ ] **6. Show message to user** — present commit message for approval before proceeding
|
|
57
|
+
- [ ] **6. Show message to user** — present commit message for approval before proceeding (skipped in `--auto`: commit immediately)
|
|
42
58
|
- [ ] **7. MANDATORY: Pre-commit preparation** — run `nvm use 18` (legacy Node.js version)
|
|
43
59
|
- [ ] **8. Create commit** — execute `git commit` with the approved message
|
|
44
60
|
- [ ] **9. Parallelization analysis (optional)** — fetch Linear comments, search for orchestration plan, delegate to `shared-parallelization-analyzer` if found
|
|
@@ -198,7 +214,7 @@ After the commit is created, perform an optional parallelization analysis:
|
|
|
198
214
|
3. Select scope based on the primary area of code changes
|
|
199
215
|
4. If task type is unclear, analyze the code changes to determine type
|
|
200
216
|
5. Always include the Linear task reference in the footer
|
|
201
|
-
6. If there are no staged changes, warn the user and don't create commit
|
|
217
|
+
6. If there are no staged changes, warn the user and don't create commit (default mode only; in `--auto` stage task-related working-tree changes automatically per Auto Mode and proceed)
|
|
202
218
|
7. After a successful commit, run the optional parallelization analysis (Step 6) to surface optimization opportunities from the orchestration plan. Recurring patterns are filed as Linear issues automatically via `linear-suggestion` skill
|
|
203
219
|
|
|
204
220
|
### Example
|
|
@@ -212,4 +228,4 @@ For Linear task "ENG-123: Add dark mode toggle to settings":
|
|
|
212
228
|
|
|
213
229
|
---
|
|
214
230
|
|
|
215
|
-
**Important**: Before committing, show the generated commit message to the user for approval.
|
|
231
|
+
**Important**: Before committing, show the generated commit message to the user for approval. In `--auto` mode skip the approval entirely — commit immediately and never end the run with a question (see Auto Mode).
|