@programinglive/dev-workflow-mcp-server 1.5.2 → 1.5.4
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/.agent/workflows/dev-workflow-bugfix.md +250 -250
- package/.agent/workflows/dev-workflow-feature.md +201 -201
- package/.agent/workflows/dev-workflow-full-cycle.md +400 -400
- package/.agent/workflows/dev-workflow-refactor.md +238 -238
- package/.github/ISSUE_TEMPLATE/bug_report.md +34 -34
- package/.github/ISSUE_TEMPLATE/feature_request.md +25 -25
- package/.github/pull_request_template.md +22 -22
- package/.github/workflows/github-release.yml +56 -0
- package/.github/workflows/npm-publish.yml +50 -50
- package/.husky/commit-msg +0 -0
- package/CHANGELOG.md +759 -741
- package/CODE_OF_CONDUCT.md +79 -79
- package/CONTRIBUTING.md +60 -60
- package/LICENSE +21 -21
- package/README.md +632 -632
- package/SECURITY.md +20 -20
- package/db/index.js +204 -204
- package/docs/NETLIFY_DEPLOYMENT.md +125 -125
- package/docs/PLESK_DEPLOYMENT.md +170 -170
- package/docs/WORKFLOW-BEST-PRACTICES.md +58 -58
- package/docs/antigravity/EXAMPLES.md +535 -535
- package/docs/antigravity/GETTING-STARTED.md +292 -292
- package/docs/antigravity/TROUBLESHOOTING.md +742 -742
- package/docs/antigravity/WALKTHROUGH.md +25 -25
- package/docs/antigravity/WORKFLOW-TEMPLATES.md +670 -670
- package/docs/product/PRD.md +67 -67
- package/docs/release-notes/RELEASE_NOTES.md +233 -226
- package/docs/web-dashboard.md +175 -175
- package/exec.js +49 -49
- package/index.js +279 -279
- package/install.js +73 -73
- package/package.json +4 -4
- package/release-wrapper.js +192 -192
- package/scripts/build-docs.js +63 -63
- package/scripts/extract-release-notes.cjs +78 -0
- package/scripts/hello-world.js +1 -1
- package/scripts/release.cjs +252 -252
- package/scripts/release.js +252 -0
- package/scripts/update-release-notes.cjs +178 -178
- package/scripts/update-release-notes.js +182 -0
- package/server.json +23 -23
- package/tailwind.config.js +8 -8
- package/tests/build.test.js +83 -83
- package/tests/exec.test.js +35 -35
- package/tests/handlers.test.js +1058 -1058
- package/tests/hello-world.test.js +13 -13
- package/tests/mcpRegistry.test.js +65 -65
- package/tests/patch-release.test.js +7 -0
- package/tests/release-wrapper.test.js +107 -107
- package/tests/workflowState.test.js +505 -505
- package/tools/definitions.js +332 -332
- package/tools/handlers.js +1019 -1019
- package/vite.config.js +43 -43
- package/vite.web.config.js +23 -23
- package/web/README.md +36 -36
- package/web/app/docs/page.tsx +202 -202
- package/web/app/globals.css +90 -90
- package/web/app/layout.tsx +36 -36
- package/web/app/page.tsx +15 -15
- package/web/components/ApiReference.tsx +20 -20
- package/web/components/Features.tsx +61 -61
- package/web/components/Footer.tsx +9 -9
- package/web/components/Hero.tsx +96 -96
- package/web/components/History.tsx +143 -143
- package/web/components/Navbar.tsx +64 -64
- package/web/components/Terminal.tsx +114 -114
- package/web/eslint.config.mjs +18 -18
- package/web/lib/db.js +131 -131
- package/web/lib/docs.js +73 -73
- package/web/netlify.toml +3 -3
- package/web/next.config.ts +12 -12
- package/web/package-lock.json +6560 -6560
- package/web/package.json +28 -28
- package/web/postcss.config.mjs +9 -9
- package/web/server.js +31 -31
- package/web/tailwind.config.ts +19 -19
- package/web/tsconfig.json +42 -42
- package/workflow-state.js +612 -612
|
@@ -1,250 +1,250 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Bug fix workflow using dev-workflow MCP server
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Bug Fix Workflow
|
|
6
|
-
|
|
7
|
-
This workflow guides you through fixing bugs with the dev-workflow MCP server, ensuring proper testing and documentation.
|
|
8
|
-
|
|
9
|
-
## When to Use
|
|
10
|
-
|
|
11
|
-
- Fixing defects
|
|
12
|
-
-修复 unexpected behavior
|
|
13
|
-
- Addressing user-reported issues
|
|
14
|
-
- Fixing regressions
|
|
15
|
-
|
|
16
|
-
## Workflow Steps
|
|
17
|
-
|
|
18
|
-
### 1. Start the Task
|
|
19
|
-
|
|
20
|
-
Begin by defining the bug:
|
|
21
|
-
|
|
22
|
-
```
|
|
23
|
-
Use start_task tool:
|
|
24
|
-
- description: "Fix [bug description]"
|
|
25
|
-
- type: "bugfix"
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
### 2. Reproduce and Fix
|
|
29
|
-
|
|
30
|
-
1. **Reproduce** the bug locally
|
|
31
|
-
2. **Identify** the root cause
|
|
32
|
-
3. **Fix** the issue
|
|
33
|
-
4. **Verify** the fix works
|
|
34
|
-
|
|
35
|
-
Tips:
|
|
36
|
-
- Document expected vs actual behavior
|
|
37
|
-
- Take notes on the root cause
|
|
38
|
-
- Test edge cases
|
|
39
|
-
|
|
40
|
-
### 3. Mark as Fixed
|
|
41
|
-
|
|
42
|
-
Once the fix is implemented:
|
|
43
|
-
|
|
44
|
-
```
|
|
45
|
-
Use mark_bug_fixed tool:
|
|
46
|
-
- summary: "[Brief description of the fix]"
|
|
47
|
-
```
|
|
48
|
-
|
|
49
|
-
### 4. Create Regression Tests
|
|
50
|
-
|
|
51
|
-
**Critical:** Write tests that would have caught this bug!
|
|
52
|
-
|
|
53
|
-
Create regression tests:
|
|
54
|
-
- Test the specific bug scenario
|
|
55
|
-
- Test edge cases around the bug
|
|
56
|
-
- Update existing tests if needed
|
|
57
|
-
|
|
58
|
-
Then mark tests as created:
|
|
59
|
-
|
|
60
|
-
```
|
|
61
|
-
Use create_tests tool
|
|
62
|
-
```
|
|
63
|
-
|
|
64
|
-
### 5. Run Tests
|
|
65
|
-
|
|
66
|
-
// turbo
|
|
67
|
-
Execute your test suite:
|
|
68
|
-
|
|
69
|
-
```bash
|
|
70
|
-
npm test
|
|
71
|
-
```
|
|
72
|
-
|
|
73
|
-
Ensure the new regression tests pass:
|
|
74
|
-
|
|
75
|
-
```
|
|
76
|
-
Use run_tests tool:
|
|
77
|
-
- passed: true
|
|
78
|
-
- testCommand: "npm test"
|
|
79
|
-
- details: "[Include regression test results]"
|
|
80
|
-
```
|
|
81
|
-
|
|
82
|
-
### 6. Document the Fix
|
|
83
|
-
|
|
84
|
-
Update documentation:
|
|
85
|
-
- **CHANGELOG** - Add bug fix entry
|
|
86
|
-
- **Code comments** - Explain why the fix was necessary
|
|
87
|
-
- **Issue tracker** - Reference issue number
|
|
88
|
-
|
|
89
|
-
```
|
|
90
|
-
Use create_documentation tool:
|
|
91
|
-
- documentationType: "changelog"
|
|
92
|
-
- summary: "[What you documented]"
|
|
93
|
-
```
|
|
94
|
-
|
|
95
|
-
### 7. Commit and Push
|
|
96
|
-
|
|
97
|
-
Use conventional commit with `fix` type:
|
|
98
|
-
|
|
99
|
-
```
|
|
100
|
-
Use commit_and_push tool:
|
|
101
|
-
- commitMessage: "fix([scope]): [description]"
|
|
102
|
-
```
|
|
103
|
-
|
|
104
|
-
Examples:
|
|
105
|
-
- `fix(auth): prevent token expiration edge case`
|
|
106
|
-
- `fix(ui): correct button alignment on mobile`
|
|
107
|
-
|
|
108
|
-
### 8. Perform Release
|
|
109
|
-
|
|
110
|
-
Bug fixes are patch releases:
|
|
111
|
-
|
|
112
|
-
```
|
|
113
|
-
Use perform_release tool:
|
|
114
|
-
- command: "npm run release:patch"
|
|
115
|
-
- notes: "v[X.Y.Z] - Bugfix for [issue]"
|
|
116
|
-
```
|
|
117
|
-
|
|
118
|
-
### 9. Complete Task
|
|
119
|
-
|
|
120
|
-
```
|
|
121
|
-
Use complete_task tool:
|
|
122
|
-
- commitMessage: "fix([scope]): [description]"
|
|
123
|
-
```
|
|
124
|
-
|
|
125
|
-
## Example: Date Formatting Bug
|
|
126
|
-
|
|
127
|
-
```
|
|
128
|
-
1. start_task:
|
|
129
|
-
description: "Fix incorrect date format in transaction history"
|
|
130
|
-
type: "bugfix"
|
|
131
|
-
|
|
132
|
-
2. [Reproduce bug, find issue in formatDate.js, implement fix]
|
|
133
|
-
|
|
134
|
-
3. mark_bug_fixed:
|
|
135
|
-
summary: "Corrected date formatting to use ISO 8601 format"
|
|
136
|
-
|
|
137
|
-
4. [Write regression test in formatDate.test.js]
|
|
138
|
-
|
|
139
|
-
5. create_tests
|
|
140
|
-
|
|
141
|
-
6. Run: npm test
|
|
142
|
-
|
|
143
|
-
7. run_tests:
|
|
144
|
-
passed: true
|
|
145
|
-
testCommand: "npm test -- utils/formatDate.test.js"
|
|
146
|
-
details: "2 new regression tests pass, all 45 tests pass"
|
|
147
|
-
|
|
148
|
-
8. [Update CHANGELOG.md with fix entry]
|
|
149
|
-
|
|
150
|
-
9. create_documentation:
|
|
151
|
-
documentationType: "changelog"
|
|
152
|
-
summary: "Added bug fix entry for date formatting issue"
|
|
153
|
-
|
|
154
|
-
10. commit_and_push:
|
|
155
|
-
commitMessage: "fix(utils): correct date formatting to use ISO 8601"
|
|
156
|
-
|
|
157
|
-
11. perform_release:
|
|
158
|
-
command: "npm run release:patch"
|
|
159
|
-
notes: "v1.2.1 - Date formatting hotfix"
|
|
160
|
-
|
|
161
|
-
12. complete_task:
|
|
162
|
-
commitMessage: "fix(utils): correct date formatting to use ISO 8601"
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
## Handling Test Failures
|
|
166
|
-
|
|
167
|
-
If tests fail during development:
|
|
168
|
-
|
|
169
|
-
```
|
|
170
|
-
run_tests:
|
|
171
|
-
passed: false
|
|
172
|
-
testCommand: "npm test"
|
|
173
|
-
details: "3 tests failed in auth module"
|
|
174
|
-
```
|
|
175
|
-
|
|
176
|
-
Response:
|
|
177
|
-
```
|
|
178
|
-
❌ Tests FAILED!
|
|
179
|
-
🚫 Cannot proceed with failing tests
|
|
180
|
-
```
|
|
181
|
-
|
|
182
|
-
Fix the issues, then re-run:
|
|
183
|
-
|
|
184
|
-
```
|
|
185
|
-
run_tests:
|
|
186
|
-
passed: true
|
|
187
|
-
testCommand: "npm test"
|
|
188
|
-
details: "All tests now pass"
|
|
189
|
-
```
|
|
190
|
-
|
|
191
|
-
## Quick Reference
|
|
192
|
-
|
|
193
|
-
```
|
|
194
|
-
1. start_task → 2. Reproduce & fix → 3. mark_bug_fixed
|
|
195
|
-
→ 4. Write regression tests → 5. create_tests → 6. run_tests
|
|
196
|
-
→ 7. Document → 8. create_documentation → 9. commit_and_push
|
|
197
|
-
→ 10. perform_release → 11. complete_task
|
|
198
|
-
```
|
|
199
|
-
|
|
200
|
-
## Tips
|
|
201
|
-
|
|
202
|
-
- **Regression tests** - Always write tests that would catch this bug
|
|
203
|
-
- **Root cause** - Fix the underlying issue, not just symptoms
|
|
204
|
-
- **Documentation** - Update CHANGELOG for user visibility
|
|
205
|
-
- **Patch versions** - Bug fixes bump patch version (X.Y.Z)
|
|
206
|
-
- **Conventional commits** - Use `fix` prefix
|
|
207
|
-
|
|
208
|
-
## Hotfix Workflow
|
|
209
|
-
|
|
210
|
-
For critical production bugs:
|
|
211
|
-
|
|
212
|
-
```
|
|
213
|
-
start_task:
|
|
214
|
-
description: "HOTFIX: [critical issue]"
|
|
215
|
-
type: "bugfix"
|
|
216
|
-
|
|
217
|
-
[Implement minimal fix]
|
|
218
|
-
|
|
219
|
-
mark_bug_fixed:
|
|
220
|
-
summary: "[Fix description]"
|
|
221
|
-
|
|
222
|
-
[Focused regression test]
|
|
223
|
-
|
|
224
|
-
create_tests
|
|
225
|
-
|
|
226
|
-
run_tests:
|
|
227
|
-
passed: true
|
|
228
|
-
testCommand: "npm test -- [critical-path]"
|
|
229
|
-
details: "[Critical tests pass]"
|
|
230
|
-
|
|
231
|
-
create_documentation:
|
|
232
|
-
documentationType: "changelog"
|
|
233
|
-
summary: "HOTFIX: [issue] - [fix]"
|
|
234
|
-
|
|
235
|
-
commit_and_push:
|
|
236
|
-
commitMessage: "fix([scope])!: HOTFIX - [description]"
|
|
237
|
-
|
|
238
|
-
perform_release:
|
|
239
|
-
command: "npm run release:patch"
|
|
240
|
-
notes: "v[X.Y.Z] - HOTFIX: [issue]"
|
|
241
|
-
|
|
242
|
-
complete_task:
|
|
243
|
-
commitMessage: "fix([scope])!: HOTFIX - [description]"
|
|
244
|
-
```
|
|
245
|
-
|
|
246
|
-
## Need Help?
|
|
247
|
-
|
|
248
|
-
- `get_workflow_status` - Check current phase
|
|
249
|
-
- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Detailed examples
|
|
250
|
-
- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues
|
|
1
|
+
---
|
|
2
|
+
description: Bug fix workflow using dev-workflow MCP server
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Bug Fix Workflow
|
|
6
|
+
|
|
7
|
+
This workflow guides you through fixing bugs with the dev-workflow MCP server, ensuring proper testing and documentation.
|
|
8
|
+
|
|
9
|
+
## When to Use
|
|
10
|
+
|
|
11
|
+
- Fixing defects
|
|
12
|
+
-修复 unexpected behavior
|
|
13
|
+
- Addressing user-reported issues
|
|
14
|
+
- Fixing regressions
|
|
15
|
+
|
|
16
|
+
## Workflow Steps
|
|
17
|
+
|
|
18
|
+
### 1. Start the Task
|
|
19
|
+
|
|
20
|
+
Begin by defining the bug:
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
Use start_task tool:
|
|
24
|
+
- description: "Fix [bug description]"
|
|
25
|
+
- type: "bugfix"
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
### 2. Reproduce and Fix
|
|
29
|
+
|
|
30
|
+
1. **Reproduce** the bug locally
|
|
31
|
+
2. **Identify** the root cause
|
|
32
|
+
3. **Fix** the issue
|
|
33
|
+
4. **Verify** the fix works
|
|
34
|
+
|
|
35
|
+
Tips:
|
|
36
|
+
- Document expected vs actual behavior
|
|
37
|
+
- Take notes on the root cause
|
|
38
|
+
- Test edge cases
|
|
39
|
+
|
|
40
|
+
### 3. Mark as Fixed
|
|
41
|
+
|
|
42
|
+
Once the fix is implemented:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
Use mark_bug_fixed tool:
|
|
46
|
+
- summary: "[Brief description of the fix]"
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
### 4. Create Regression Tests
|
|
50
|
+
|
|
51
|
+
**Critical:** Write tests that would have caught this bug!
|
|
52
|
+
|
|
53
|
+
Create regression tests:
|
|
54
|
+
- Test the specific bug scenario
|
|
55
|
+
- Test edge cases around the bug
|
|
56
|
+
- Update existing tests if needed
|
|
57
|
+
|
|
58
|
+
Then mark tests as created:
|
|
59
|
+
|
|
60
|
+
```
|
|
61
|
+
Use create_tests tool
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
### 5. Run Tests
|
|
65
|
+
|
|
66
|
+
// turbo
|
|
67
|
+
Execute your test suite:
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
npm test
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Ensure the new regression tests pass:
|
|
74
|
+
|
|
75
|
+
```
|
|
76
|
+
Use run_tests tool:
|
|
77
|
+
- passed: true
|
|
78
|
+
- testCommand: "npm test"
|
|
79
|
+
- details: "[Include regression test results]"
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
### 6. Document the Fix
|
|
83
|
+
|
|
84
|
+
Update documentation:
|
|
85
|
+
- **CHANGELOG** - Add bug fix entry
|
|
86
|
+
- **Code comments** - Explain why the fix was necessary
|
|
87
|
+
- **Issue tracker** - Reference issue number
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
Use create_documentation tool:
|
|
91
|
+
- documentationType: "changelog"
|
|
92
|
+
- summary: "[What you documented]"
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
### 7. Commit and Push
|
|
96
|
+
|
|
97
|
+
Use conventional commit with `fix` type:
|
|
98
|
+
|
|
99
|
+
```
|
|
100
|
+
Use commit_and_push tool:
|
|
101
|
+
- commitMessage: "fix([scope]): [description]"
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
Examples:
|
|
105
|
+
- `fix(auth): prevent token expiration edge case`
|
|
106
|
+
- `fix(ui): correct button alignment on mobile`
|
|
107
|
+
|
|
108
|
+
### 8. Perform Release
|
|
109
|
+
|
|
110
|
+
Bug fixes are patch releases:
|
|
111
|
+
|
|
112
|
+
```
|
|
113
|
+
Use perform_release tool:
|
|
114
|
+
- command: "npm run release:patch"
|
|
115
|
+
- notes: "v[X.Y.Z] - Bugfix for [issue]"
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
### 9. Complete Task
|
|
119
|
+
|
|
120
|
+
```
|
|
121
|
+
Use complete_task tool:
|
|
122
|
+
- commitMessage: "fix([scope]): [description]"
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
## Example: Date Formatting Bug
|
|
126
|
+
|
|
127
|
+
```
|
|
128
|
+
1. start_task:
|
|
129
|
+
description: "Fix incorrect date format in transaction history"
|
|
130
|
+
type: "bugfix"
|
|
131
|
+
|
|
132
|
+
2. [Reproduce bug, find issue in formatDate.js, implement fix]
|
|
133
|
+
|
|
134
|
+
3. mark_bug_fixed:
|
|
135
|
+
summary: "Corrected date formatting to use ISO 8601 format"
|
|
136
|
+
|
|
137
|
+
4. [Write regression test in formatDate.test.js]
|
|
138
|
+
|
|
139
|
+
5. create_tests
|
|
140
|
+
|
|
141
|
+
6. Run: npm test
|
|
142
|
+
|
|
143
|
+
7. run_tests:
|
|
144
|
+
passed: true
|
|
145
|
+
testCommand: "npm test -- utils/formatDate.test.js"
|
|
146
|
+
details: "2 new regression tests pass, all 45 tests pass"
|
|
147
|
+
|
|
148
|
+
8. [Update CHANGELOG.md with fix entry]
|
|
149
|
+
|
|
150
|
+
9. create_documentation:
|
|
151
|
+
documentationType: "changelog"
|
|
152
|
+
summary: "Added bug fix entry for date formatting issue"
|
|
153
|
+
|
|
154
|
+
10. commit_and_push:
|
|
155
|
+
commitMessage: "fix(utils): correct date formatting to use ISO 8601"
|
|
156
|
+
|
|
157
|
+
11. perform_release:
|
|
158
|
+
command: "npm run release:patch"
|
|
159
|
+
notes: "v1.2.1 - Date formatting hotfix"
|
|
160
|
+
|
|
161
|
+
12. complete_task:
|
|
162
|
+
commitMessage: "fix(utils): correct date formatting to use ISO 8601"
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
## Handling Test Failures
|
|
166
|
+
|
|
167
|
+
If tests fail during development:
|
|
168
|
+
|
|
169
|
+
```
|
|
170
|
+
run_tests:
|
|
171
|
+
passed: false
|
|
172
|
+
testCommand: "npm test"
|
|
173
|
+
details: "3 tests failed in auth module"
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
Response:
|
|
177
|
+
```
|
|
178
|
+
❌ Tests FAILED!
|
|
179
|
+
🚫 Cannot proceed with failing tests
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
Fix the issues, then re-run:
|
|
183
|
+
|
|
184
|
+
```
|
|
185
|
+
run_tests:
|
|
186
|
+
passed: true
|
|
187
|
+
testCommand: "npm test"
|
|
188
|
+
details: "All tests now pass"
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
## Quick Reference
|
|
192
|
+
|
|
193
|
+
```
|
|
194
|
+
1. start_task → 2. Reproduce & fix → 3. mark_bug_fixed
|
|
195
|
+
→ 4. Write regression tests → 5. create_tests → 6. run_tests
|
|
196
|
+
→ 7. Document → 8. create_documentation → 9. commit_and_push
|
|
197
|
+
→ 10. perform_release → 11. complete_task
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
## Tips
|
|
201
|
+
|
|
202
|
+
- **Regression tests** - Always write tests that would catch this bug
|
|
203
|
+
- **Root cause** - Fix the underlying issue, not just symptoms
|
|
204
|
+
- **Documentation** - Update CHANGELOG for user visibility
|
|
205
|
+
- **Patch versions** - Bug fixes bump patch version (X.Y.Z)
|
|
206
|
+
- **Conventional commits** - Use `fix` prefix
|
|
207
|
+
|
|
208
|
+
## Hotfix Workflow
|
|
209
|
+
|
|
210
|
+
For critical production bugs:
|
|
211
|
+
|
|
212
|
+
```
|
|
213
|
+
start_task:
|
|
214
|
+
description: "HOTFIX: [critical issue]"
|
|
215
|
+
type: "bugfix"
|
|
216
|
+
|
|
217
|
+
[Implement minimal fix]
|
|
218
|
+
|
|
219
|
+
mark_bug_fixed:
|
|
220
|
+
summary: "[Fix description]"
|
|
221
|
+
|
|
222
|
+
[Focused regression test]
|
|
223
|
+
|
|
224
|
+
create_tests
|
|
225
|
+
|
|
226
|
+
run_tests:
|
|
227
|
+
passed: true
|
|
228
|
+
testCommand: "npm test -- [critical-path]"
|
|
229
|
+
details: "[Critical tests pass]"
|
|
230
|
+
|
|
231
|
+
create_documentation:
|
|
232
|
+
documentationType: "changelog"
|
|
233
|
+
summary: "HOTFIX: [issue] - [fix]"
|
|
234
|
+
|
|
235
|
+
commit_and_push:
|
|
236
|
+
commitMessage: "fix([scope])!: HOTFIX - [description]"
|
|
237
|
+
|
|
238
|
+
perform_release:
|
|
239
|
+
command: "npm run release:patch"
|
|
240
|
+
notes: "v[X.Y.Z] - HOTFIX: [issue]"
|
|
241
|
+
|
|
242
|
+
complete_task:
|
|
243
|
+
commitMessage: "fix([scope])!: HOTFIX - [description]"
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
## Need Help?
|
|
247
|
+
|
|
248
|
+
- `get_workflow_status` - Check current phase
|
|
249
|
+
- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Detailed examples
|
|
250
|
+
- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues
|