@programinglive/dev-workflow-mcp-server 1.5.0 → 1.5.2
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/npm-publish.yml +50 -47
- package/.husky/commit-msg +0 -0
- package/CHANGELOG.md +750 -491
- package/CODE_OF_CONDUCT.md +79 -79
- package/CONTRIBUTING.md +60 -60
- package/LICENSE +21 -21
- package/README.md +632 -609
- package/SECURITY.md +20 -20
- package/db/index.js +204 -204
- package/docs/NETLIFY_DEPLOYMENT.md +125 -0
- package/docs/PLESK_DEPLOYMENT.md +170 -0
- package/docs/WORKFLOW-BEST-PRACTICES.md +58 -0
- 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 -64
- package/docs/release-notes/RELEASE_NOTES.md +226 -132
- package/docs/web-dashboard.md +175 -163
- package/exec.js +49 -49
- package/index.js +279 -279
- package/install.js +73 -73
- package/package.json +11 -9
- package/release-wrapper.js +192 -157
- package/scripts/build-docs.js +63 -63
- package/scripts/hello-world.js +1 -1
- package/scripts/release.cjs +252 -252
- package/scripts/update-release-notes.cjs +178 -182
- package/server.json +23 -0
- package/tailwind.config.js +8 -10
- package/tests/build.test.js +83 -48
- package/tests/exec.test.js +35 -35
- package/tests/handlers.test.js +1058 -980
- package/tests/hello-world.test.js +13 -13
- package/tests/mcpRegistry.test.js +65 -0
- package/tests/release-wrapper.test.js +107 -105
- package/tests/workflowState.test.js +505 -502
- package/tools/definitions.js +332 -332
- package/tools/handlers.js +1019 -1019
- package/vite.config.js +43 -43
- package/vite.web.config.js +23 -0
- package/web/README.md +36 -0
- package/web/app/docs/page.tsx +202 -0
- package/web/app/favicon.ico +0 -0
- package/web/app/globals.css +91 -0
- package/web/app/layout.tsx +36 -0
- package/web/app/page.tsx +15 -0
- package/web/components/ApiReference.tsx +20 -0
- package/web/components/Features.tsx +61 -0
- package/web/components/Footer.tsx +9 -0
- package/web/components/Hero.tsx +96 -0
- package/web/components/History.tsx +143 -0
- package/web/components/Navbar.tsx +64 -0
- package/web/components/Terminal.tsx +114 -0
- package/web/eslint.config.mjs +18 -0
- package/web/lib/db.js +131 -0
- package/web/lib/docs.js +73 -0
- package/web/netlify.toml +3 -0
- package/web/next.config.ts +12 -0
- package/web/package-lock.json +6560 -0
- package/web/package.json +28 -0
- package/web/postcss.config.mjs +9 -0
- package/web/public/assets/android-chrome-192x192.png +0 -0
- package/web/public/assets/android-chrome-512x512.png +0 -0
- package/web/public/assets/apple-touch-icon.png +0 -0
- package/web/public/assets/favicon-16x16.png +0 -0
- package/web/public/assets/favicon-32x32.png +0 -0
- package/web/public/assets/favicon.ico +0 -0
- package/web/public/assets/favicon.png +0 -0
- package/web/public/assets/logo.png +0 -0
- package/web/public/assets/og-preview.png +0 -0
- package/web/public/assets/site.webmanifest +1 -0
- package/web/public/file.svg +1 -0
- package/web/public/globe.svg +1 -0
- package/web/public/next.svg +1 -0
- package/web/public/vercel.svg +1 -0
- package/web/public/window.svg +1 -0
- package/web/server.js +31 -159
- package/web/tailwind.config.ts +19 -0
- package/web/tsconfig.json +42 -0
- package/workflow-state.js +612 -626
- package/dist/docs/EXAMPLES.html +0 -411
- package/dist/docs/GETTING-STARTED.html +0 -233
- package/dist/docs/README.html +0 -535
- package/dist/docs/RELEASE_NOTES.html +0 -167
- package/dist/docs/TROUBLESHOOTING.html +0 -542
- package/dist/docs/WORKFLOW-TEMPLATES.html +0 -591
- package/dist/docs/web-dashboard.html +0 -158
- package/web/public/index.html +0 -1046
- package/web/public/input.css +0 -3
- package/web/public/output.css +0 -1
|
@@ -1,238 +1,238 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Refactoring workflow using dev-workflow MCP server
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Refactoring Workflow
|
|
6
|
-
|
|
7
|
-
This workflow guides you through refactoring code while maintaining functionality with the dev-workflow MCP server.
|
|
8
|
-
|
|
9
|
-
## When to Use
|
|
10
|
-
|
|
11
|
-
- Improving code structure
|
|
12
|
-
- Removing code smells
|
|
13
|
-
- Optimizing performance
|
|
14
|
-
- Simplifying complex code
|
|
15
|
-
|
|
16
|
-
## Workflow Steps
|
|
17
|
-
|
|
18
|
-
### 1. Start the Task
|
|
19
|
-
|
|
20
|
-
Define your refactoring goal:
|
|
21
|
-
|
|
22
|
-
```
|
|
23
|
-
Use start_task tool:
|
|
24
|
-
- description: "Refactor [component/module] to [improvement goal]"
|
|
25
|
-
- type: "refactor"
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
### 2. Ensure Test Coverage
|
|
29
|
-
|
|
30
|
-
**Before refactoring**, verify you have good test coverage:
|
|
31
|
-
|
|
32
|
-
```bash
|
|
33
|
-
npm test -- --coverage
|
|
34
|
-
```
|
|
35
|
-
|
|
36
|
-
If coverage is low, write tests first to ensure refactoring doesn't break functionality.
|
|
37
|
-
|
|
38
|
-
### 3. Refactor Code
|
|
39
|
-
|
|
40
|
-
Make your improvements:
|
|
41
|
-
- Extract methods/components
|
|
42
|
-
- Simplify complex logic
|
|
43
|
-
- Remove duplication
|
|
44
|
-
- Optimize performance
|
|
45
|
-
|
|
46
|
-
**Key principle:** Behavior should remain unchanged.
|
|
47
|
-
|
|
48
|
-
### 4. Mark as Fixed
|
|
49
|
-
|
|
50
|
-
```
|
|
51
|
-
Use mark_bug_fixed tool:
|
|
52
|
-
- summary: "[Brief description of refactoring]"
|
|
53
|
-
```
|
|
54
|
-
|
|
55
|
-
### 5. Update Tests
|
|
56
|
-
|
|
57
|
-
Adapt tests to new structure if needed:
|
|
58
|
-
- Update test structure for new organization
|
|
59
|
-
- Ensure all existing tests still pass
|
|
60
|
-
- Add tests for new abstractions
|
|
61
|
-
|
|
62
|
-
```
|
|
63
|
-
Use create_tests tool
|
|
64
|
-
```
|
|
65
|
-
|
|
66
|
-
### 6. Run Tests
|
|
67
|
-
|
|
68
|
-
// turbo
|
|
69
|
-
Verify all tests still pass:
|
|
70
|
-
|
|
71
|
-
```bash
|
|
72
|
-
npm test -- --coverage
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
Coverage should maintain or improve:
|
|
76
|
-
|
|
77
|
-
```
|
|
78
|
-
Use run_tests tool:
|
|
79
|
-
- passed: true
|
|
80
|
-
- testCommand: "npm test -- --coverage"
|
|
81
|
-
- details: "[All tests pass, coverage maintained/improved]"
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
### 7. Document Changes
|
|
85
|
-
|
|
86
|
-
Update documentation for new structure:
|
|
87
|
-
- **Inline comments** - Document new abstractions
|
|
88
|
-
- **Architecture docs** - Update diagrams if structure changed
|
|
89
|
-
- **README** - Update examples if API changed
|
|
90
|
-
|
|
91
|
-
```
|
|
92
|
-
Use create_documentation tool:
|
|
93
|
-
- documentationType: "inline-comments"
|
|
94
|
-
- summary: "[What you documented]"
|
|
95
|
-
```
|
|
96
|
-
|
|
97
|
-
### 8. Commit and Push
|
|
98
|
-
|
|
99
|
-
Use `refactor` commit type:
|
|
100
|
-
|
|
101
|
-
```
|
|
102
|
-
Use commit_and_push tool:
|
|
103
|
-
- commitMessage: "refactor([scope]): [description]"
|
|
104
|
-
```
|
|
105
|
-
|
|
106
|
-
Examples:
|
|
107
|
-
- `refactor(auth): extract authentication logic to custom hooks`
|
|
108
|
-
- `refactor(api): simplify error handling with interceptors`
|
|
109
|
-
|
|
110
|
-
### 9. Perform Release
|
|
111
|
-
|
|
112
|
-
Refactoring can be minor or patch:
|
|
113
|
-
- **Minor** - Significant internal improvements
|
|
114
|
-
- **Patch** - Small structural improvements
|
|
115
|
-
|
|
116
|
-
```
|
|
117
|
-
Use perform_release tool:
|
|
118
|
-
- command: "npm run release:minor"
|
|
119
|
-
- notes: "v[X.Y.Z] - Internal improvements (refactoring)"
|
|
120
|
-
```
|
|
121
|
-
|
|
122
|
-
### 10. Complete Task
|
|
123
|
-
|
|
124
|
-
```
|
|
125
|
-
Use complete_task tool:
|
|
126
|
-
- commitMessage: "refactor([scope]): [description]"
|
|
127
|
-
```
|
|
128
|
-
|
|
129
|
-
## Example: Extract Custom Hooks
|
|
130
|
-
|
|
131
|
-
```
|
|
132
|
-
1. start_task:
|
|
133
|
-
description: "Refactor authentication logic into reusable custom hooks"
|
|
134
|
-
type: "refactor"
|
|
135
|
-
|
|
136
|
-
2. [Check test coverage: 89%]
|
|
137
|
-
|
|
138
|
-
3. [Extract useAuth and usePermissions hooks from components]
|
|
139
|
-
|
|
140
|
-
4. mark_bug_fixed:
|
|
141
|
-
summary: "Extracted useAuth and usePermissions hooks from component logic"
|
|
142
|
-
|
|
143
|
-
5. [Update component tests to work with hooks]
|
|
144
|
-
|
|
145
|
-
6. create_tests
|
|
146
|
-
|
|
147
|
-
7. Run: npm test -- --coverage
|
|
148
|
-
|
|
149
|
-
8. run_tests:
|
|
150
|
-
passed: true
|
|
151
|
-
testCommand: "npm test -- --coverage"
|
|
152
|
-
details: "All 145 tests pass, coverage improved from 89% to 92%"
|
|
153
|
-
|
|
154
|
-
9. [Add JSDoc comments to hooks, update README with hook examples]
|
|
155
|
-
|
|
156
|
-
10. create_documentation:
|
|
157
|
-
documentationType: "inline-comments"
|
|
158
|
-
summary: "Added JSDoc for custom hooks and usage examples in README"
|
|
159
|
-
|
|
160
|
-
11. commit_and_push:
|
|
161
|
-
commitMessage: "refactor(auth): extract authentication logic to custom hooks"
|
|
162
|
-
|
|
163
|
-
12. perform_release:
|
|
164
|
-
command: "npm run release:minor"
|
|
165
|
-
notes: "v1.6.0 - Authentication refactoring (improved maintainability)"
|
|
166
|
-
|
|
167
|
-
13. complete_task:
|
|
168
|
-
commitMessage: "refactor(auth): extract authentication logic to custom hooks"
|
|
169
|
-
```
|
|
170
|
-
|
|
171
|
-
## Refactoring Checklist
|
|
172
|
-
|
|
173
|
-
Before starting:
|
|
174
|
-
- [ ] Current code has adequate test coverage
|
|
175
|
-
- [ ] Tests are passing
|
|
176
|
-
- [ ] Refactoring goal is clear
|
|
177
|
-
|
|
178
|
-
During refactoring:
|
|
179
|
-
- [ ] Run tests frequently
|
|
180
|
-
- [ ] Make small, incremental changes
|
|
181
|
-
- [ ] Commit logical chunks if needed locally
|
|
182
|
-
|
|
183
|
-
After refactoring:
|
|
184
|
-
- [ ] All tests pass
|
|
185
|
-
- [ ] Coverage maintained or improved
|
|
186
|
-
- [ ] Code is simpler/cleaner
|
|
187
|
-
- [ ] Documentation updated
|
|
188
|
-
|
|
189
|
-
## Quick Reference
|
|
190
|
-
|
|
191
|
-
```
|
|
192
|
-
1. start_task → 2. Verify tests → 3. Refactor → 4. mark_bug_fixed
|
|
193
|
-
→ 5. Update tests → 6. create_tests → 7. run_tests
|
|
194
|
-
→ 8. Document → 9. create_documentation → 10. commit_and_push
|
|
195
|
-
→ 11. perform_release → 12. complete_task
|
|
196
|
-
```
|
|
197
|
-
|
|
198
|
-
## Tips
|
|
199
|
-
|
|
200
|
-
- **Test first** - Ensure good coverage before refactoring
|
|
201
|
-
- **Small changes** - Refactor incrementally
|
|
202
|
-
- **Keep tests passing** - Run tests frequently
|
|
203
|
-
- **No behavior changes** - Functionality stays the same
|
|
204
|
-
- **Document abstractions** - Explain new patterns
|
|
205
|
-
- **Coverage goal** - Maintain or improve test coverage
|
|
206
|
-
|
|
207
|
-
## Common Refactoring Patterns
|
|
208
|
-
|
|
209
|
-
### Extract Method
|
|
210
|
-
```
|
|
211
|
-
refactor(utils): extract validation logic to separate functions
|
|
212
|
-
```
|
|
213
|
-
|
|
214
|
-
### Extract Component
|
|
215
|
-
```
|
|
216
|
-
refactor(ui): extract UserCard component from UserList
|
|
217
|
-
```
|
|
218
|
-
|
|
219
|
-
### Simplify Logic
|
|
220
|
-
```
|
|
221
|
-
refactor(cart): simplify price calculation logic
|
|
222
|
-
```
|
|
223
|
-
|
|
224
|
-
### Remove Duplication
|
|
225
|
-
```
|
|
226
|
-
refactor(api): consolidate duplicate request handlers
|
|
227
|
-
```
|
|
228
|
-
|
|
229
|
-
### Optimize Performance
|
|
230
|
-
```
|
|
231
|
-
refactor(search): optimize search algorithm complexity
|
|
232
|
-
```
|
|
233
|
-
|
|
234
|
-
## Need Help?
|
|
235
|
-
|
|
236
|
-
- `get_workflow_status` - Check current phase
|
|
237
|
-
- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Refactoring examples
|
|
238
|
-
- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues
|
|
1
|
+
---
|
|
2
|
+
description: Refactoring workflow using dev-workflow MCP server
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Refactoring Workflow
|
|
6
|
+
|
|
7
|
+
This workflow guides you through refactoring code while maintaining functionality with the dev-workflow MCP server.
|
|
8
|
+
|
|
9
|
+
## When to Use
|
|
10
|
+
|
|
11
|
+
- Improving code structure
|
|
12
|
+
- Removing code smells
|
|
13
|
+
- Optimizing performance
|
|
14
|
+
- Simplifying complex code
|
|
15
|
+
|
|
16
|
+
## Workflow Steps
|
|
17
|
+
|
|
18
|
+
### 1. Start the Task
|
|
19
|
+
|
|
20
|
+
Define your refactoring goal:
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
Use start_task tool:
|
|
24
|
+
- description: "Refactor [component/module] to [improvement goal]"
|
|
25
|
+
- type: "refactor"
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
### 2. Ensure Test Coverage
|
|
29
|
+
|
|
30
|
+
**Before refactoring**, verify you have good test coverage:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
npm test -- --coverage
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
If coverage is low, write tests first to ensure refactoring doesn't break functionality.
|
|
37
|
+
|
|
38
|
+
### 3. Refactor Code
|
|
39
|
+
|
|
40
|
+
Make your improvements:
|
|
41
|
+
- Extract methods/components
|
|
42
|
+
- Simplify complex logic
|
|
43
|
+
- Remove duplication
|
|
44
|
+
- Optimize performance
|
|
45
|
+
|
|
46
|
+
**Key principle:** Behavior should remain unchanged.
|
|
47
|
+
|
|
48
|
+
### 4. Mark as Fixed
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
Use mark_bug_fixed tool:
|
|
52
|
+
- summary: "[Brief description of refactoring]"
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
### 5. Update Tests
|
|
56
|
+
|
|
57
|
+
Adapt tests to new structure if needed:
|
|
58
|
+
- Update test structure for new organization
|
|
59
|
+
- Ensure all existing tests still pass
|
|
60
|
+
- Add tests for new abstractions
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
Use create_tests tool
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
### 6. Run Tests
|
|
67
|
+
|
|
68
|
+
// turbo
|
|
69
|
+
Verify all tests still pass:
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
npm test -- --coverage
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Coverage should maintain or improve:
|
|
76
|
+
|
|
77
|
+
```
|
|
78
|
+
Use run_tests tool:
|
|
79
|
+
- passed: true
|
|
80
|
+
- testCommand: "npm test -- --coverage"
|
|
81
|
+
- details: "[All tests pass, coverage maintained/improved]"
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
### 7. Document Changes
|
|
85
|
+
|
|
86
|
+
Update documentation for new structure:
|
|
87
|
+
- **Inline comments** - Document new abstractions
|
|
88
|
+
- **Architecture docs** - Update diagrams if structure changed
|
|
89
|
+
- **README** - Update examples if API changed
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
Use create_documentation tool:
|
|
93
|
+
- documentationType: "inline-comments"
|
|
94
|
+
- summary: "[What you documented]"
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
### 8. Commit and Push
|
|
98
|
+
|
|
99
|
+
Use `refactor` commit type:
|
|
100
|
+
|
|
101
|
+
```
|
|
102
|
+
Use commit_and_push tool:
|
|
103
|
+
- commitMessage: "refactor([scope]): [description]"
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
Examples:
|
|
107
|
+
- `refactor(auth): extract authentication logic to custom hooks`
|
|
108
|
+
- `refactor(api): simplify error handling with interceptors`
|
|
109
|
+
|
|
110
|
+
### 9. Perform Release
|
|
111
|
+
|
|
112
|
+
Refactoring can be minor or patch:
|
|
113
|
+
- **Minor** - Significant internal improvements
|
|
114
|
+
- **Patch** - Small structural improvements
|
|
115
|
+
|
|
116
|
+
```
|
|
117
|
+
Use perform_release tool:
|
|
118
|
+
- command: "npm run release:minor"
|
|
119
|
+
- notes: "v[X.Y.Z] - Internal improvements (refactoring)"
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
### 10. Complete Task
|
|
123
|
+
|
|
124
|
+
```
|
|
125
|
+
Use complete_task tool:
|
|
126
|
+
- commitMessage: "refactor([scope]): [description]"
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
## Example: Extract Custom Hooks
|
|
130
|
+
|
|
131
|
+
```
|
|
132
|
+
1. start_task:
|
|
133
|
+
description: "Refactor authentication logic into reusable custom hooks"
|
|
134
|
+
type: "refactor"
|
|
135
|
+
|
|
136
|
+
2. [Check test coverage: 89%]
|
|
137
|
+
|
|
138
|
+
3. [Extract useAuth and usePermissions hooks from components]
|
|
139
|
+
|
|
140
|
+
4. mark_bug_fixed:
|
|
141
|
+
summary: "Extracted useAuth and usePermissions hooks from component logic"
|
|
142
|
+
|
|
143
|
+
5. [Update component tests to work with hooks]
|
|
144
|
+
|
|
145
|
+
6. create_tests
|
|
146
|
+
|
|
147
|
+
7. Run: npm test -- --coverage
|
|
148
|
+
|
|
149
|
+
8. run_tests:
|
|
150
|
+
passed: true
|
|
151
|
+
testCommand: "npm test -- --coverage"
|
|
152
|
+
details: "All 145 tests pass, coverage improved from 89% to 92%"
|
|
153
|
+
|
|
154
|
+
9. [Add JSDoc comments to hooks, update README with hook examples]
|
|
155
|
+
|
|
156
|
+
10. create_documentation:
|
|
157
|
+
documentationType: "inline-comments"
|
|
158
|
+
summary: "Added JSDoc for custom hooks and usage examples in README"
|
|
159
|
+
|
|
160
|
+
11. commit_and_push:
|
|
161
|
+
commitMessage: "refactor(auth): extract authentication logic to custom hooks"
|
|
162
|
+
|
|
163
|
+
12. perform_release:
|
|
164
|
+
command: "npm run release:minor"
|
|
165
|
+
notes: "v1.6.0 - Authentication refactoring (improved maintainability)"
|
|
166
|
+
|
|
167
|
+
13. complete_task:
|
|
168
|
+
commitMessage: "refactor(auth): extract authentication logic to custom hooks"
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
## Refactoring Checklist
|
|
172
|
+
|
|
173
|
+
Before starting:
|
|
174
|
+
- [ ] Current code has adequate test coverage
|
|
175
|
+
- [ ] Tests are passing
|
|
176
|
+
- [ ] Refactoring goal is clear
|
|
177
|
+
|
|
178
|
+
During refactoring:
|
|
179
|
+
- [ ] Run tests frequently
|
|
180
|
+
- [ ] Make small, incremental changes
|
|
181
|
+
- [ ] Commit logical chunks if needed locally
|
|
182
|
+
|
|
183
|
+
After refactoring:
|
|
184
|
+
- [ ] All tests pass
|
|
185
|
+
- [ ] Coverage maintained or improved
|
|
186
|
+
- [ ] Code is simpler/cleaner
|
|
187
|
+
- [ ] Documentation updated
|
|
188
|
+
|
|
189
|
+
## Quick Reference
|
|
190
|
+
|
|
191
|
+
```
|
|
192
|
+
1. start_task → 2. Verify tests → 3. Refactor → 4. mark_bug_fixed
|
|
193
|
+
→ 5. Update tests → 6. create_tests → 7. run_tests
|
|
194
|
+
→ 8. Document → 9. create_documentation → 10. commit_and_push
|
|
195
|
+
→ 11. perform_release → 12. complete_task
|
|
196
|
+
```
|
|
197
|
+
|
|
198
|
+
## Tips
|
|
199
|
+
|
|
200
|
+
- **Test first** - Ensure good coverage before refactoring
|
|
201
|
+
- **Small changes** - Refactor incrementally
|
|
202
|
+
- **Keep tests passing** - Run tests frequently
|
|
203
|
+
- **No behavior changes** - Functionality stays the same
|
|
204
|
+
- **Document abstractions** - Explain new patterns
|
|
205
|
+
- **Coverage goal** - Maintain or improve test coverage
|
|
206
|
+
|
|
207
|
+
## Common Refactoring Patterns
|
|
208
|
+
|
|
209
|
+
### Extract Method
|
|
210
|
+
```
|
|
211
|
+
refactor(utils): extract validation logic to separate functions
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
### Extract Component
|
|
215
|
+
```
|
|
216
|
+
refactor(ui): extract UserCard component from UserList
|
|
217
|
+
```
|
|
218
|
+
|
|
219
|
+
### Simplify Logic
|
|
220
|
+
```
|
|
221
|
+
refactor(cart): simplify price calculation logic
|
|
222
|
+
```
|
|
223
|
+
|
|
224
|
+
### Remove Duplication
|
|
225
|
+
```
|
|
226
|
+
refactor(api): consolidate duplicate request handlers
|
|
227
|
+
```
|
|
228
|
+
|
|
229
|
+
### Optimize Performance
|
|
230
|
+
```
|
|
231
|
+
refactor(search): optimize search algorithm complexity
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
## Need Help?
|
|
235
|
+
|
|
236
|
+
- `get_workflow_status` - Check current phase
|
|
237
|
+
- [EXAMPLES.md](../docs/antigravity/EXAMPLES.md) - Refactoring examples
|
|
238
|
+
- [TROUBLESHOOTING.md](../docs/antigravity/TROUBLESHOOTING.md) - Common issues
|
|
@@ -1,34 +1,34 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: Bug Report
|
|
3
|
-
about: Create a report to help us improve
|
|
4
|
-
labels: bug
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Describe the bug
|
|
8
|
-
|
|
9
|
-
A clear and concise description of what the bug is.
|
|
10
|
-
|
|
11
|
-
## To Reproduce
|
|
12
|
-
|
|
13
|
-
Steps to reproduce the behavior:
|
|
14
|
-
1. Go to '...'
|
|
15
|
-
2. Run command '...'
|
|
16
|
-
3. See error
|
|
17
|
-
|
|
18
|
-
## Expected behavior
|
|
19
|
-
|
|
20
|
-
A clear and concise description of what you expected to happen.
|
|
21
|
-
|
|
22
|
-
## Screenshots / Logs
|
|
23
|
-
|
|
24
|
-
If applicable, add screenshots or paste logs to help explain your problem.
|
|
25
|
-
|
|
26
|
-
## Environment (please complete the following information):
|
|
27
|
-
|
|
28
|
-
- OS: [e.g. macOS 14.5]
|
|
29
|
-
- Node version: [e.g. 20.14.0]
|
|
30
|
-
- npm version: [e.g. 10.8.2]
|
|
31
|
-
|
|
32
|
-
## Additional context
|
|
33
|
-
|
|
34
|
-
Add any other context about the problem here.
|
|
1
|
+
---
|
|
2
|
+
name: Bug Report
|
|
3
|
+
about: Create a report to help us improve
|
|
4
|
+
labels: bug
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Describe the bug
|
|
8
|
+
|
|
9
|
+
A clear and concise description of what the bug is.
|
|
10
|
+
|
|
11
|
+
## To Reproduce
|
|
12
|
+
|
|
13
|
+
Steps to reproduce the behavior:
|
|
14
|
+
1. Go to '...'
|
|
15
|
+
2. Run command '...'
|
|
16
|
+
3. See error
|
|
17
|
+
|
|
18
|
+
## Expected behavior
|
|
19
|
+
|
|
20
|
+
A clear and concise description of what you expected to happen.
|
|
21
|
+
|
|
22
|
+
## Screenshots / Logs
|
|
23
|
+
|
|
24
|
+
If applicable, add screenshots or paste logs to help explain your problem.
|
|
25
|
+
|
|
26
|
+
## Environment (please complete the following information):
|
|
27
|
+
|
|
28
|
+
- OS: [e.g. macOS 14.5]
|
|
29
|
+
- Node version: [e.g. 20.14.0]
|
|
30
|
+
- npm version: [e.g. 10.8.2]
|
|
31
|
+
|
|
32
|
+
## Additional context
|
|
33
|
+
|
|
34
|
+
Add any other context about the problem here.
|
|
@@ -1,25 +1,25 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: Feature Request
|
|
3
|
-
about: Suggest an idea for this project
|
|
4
|
-
labels: enhancement
|
|
5
|
-
---
|
|
6
|
-
|
|
7
|
-
## Summary
|
|
8
|
-
|
|
9
|
-
Describe the feature you'd like to see added.
|
|
10
|
-
|
|
11
|
-
## Problem Statement
|
|
12
|
-
|
|
13
|
-
What problem does this feature solve? Why is it important?
|
|
14
|
-
|
|
15
|
-
## Proposed Solution
|
|
16
|
-
|
|
17
|
-
Describe how you think this should work.
|
|
18
|
-
|
|
19
|
-
## Alternatives Considered
|
|
20
|
-
|
|
21
|
-
List any alternative solutions or features you've considered.
|
|
22
|
-
|
|
23
|
-
## Additional context
|
|
24
|
-
|
|
25
|
-
Add any other context, screenshots, or references about the feature request here.
|
|
1
|
+
---
|
|
2
|
+
name: Feature Request
|
|
3
|
+
about: Suggest an idea for this project
|
|
4
|
+
labels: enhancement
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Summary
|
|
8
|
+
|
|
9
|
+
Describe the feature you'd like to see added.
|
|
10
|
+
|
|
11
|
+
## Problem Statement
|
|
12
|
+
|
|
13
|
+
What problem does this feature solve? Why is it important?
|
|
14
|
+
|
|
15
|
+
## Proposed Solution
|
|
16
|
+
|
|
17
|
+
Describe how you think this should work.
|
|
18
|
+
|
|
19
|
+
## Alternatives Considered
|
|
20
|
+
|
|
21
|
+
List any alternative solutions or features you've considered.
|
|
22
|
+
|
|
23
|
+
## Additional context
|
|
24
|
+
|
|
25
|
+
Add any other context, screenshots, or references about the feature request here.
|
|
@@ -1,22 +1,22 @@
|
|
|
1
|
-
# Summary
|
|
2
|
-
|
|
3
|
-
- Describe the changes introduced by this PR.
|
|
4
|
-
- Reference any related issues (e.g., `Closes #123`).
|
|
5
|
-
|
|
6
|
-
# Testing
|
|
7
|
-
|
|
8
|
-
- [ ] `npm test`
|
|
9
|
-
- [ ] Other (specify):
|
|
10
|
-
|
|
11
|
-
# Documentation
|
|
12
|
-
|
|
13
|
-
- [ ] README updated
|
|
14
|
-
- [ ] Other docs updated (specify):
|
|
15
|
-
|
|
16
|
-
# Checklist
|
|
17
|
-
|
|
18
|
-
- [ ] Followed the development workflow enforced by the MCP server
|
|
19
|
-
- [ ] Added/updated tests as needed
|
|
20
|
-
- [ ] Verified single data/event/command/effect/validation/permission/authorization/error/success/warning/info flows remain intact
|
|
21
|
-
- [ ] Removed unused imports and console statements
|
|
22
|
-
- [ ] Ready for review
|
|
1
|
+
# Summary
|
|
2
|
+
|
|
3
|
+
- Describe the changes introduced by this PR.
|
|
4
|
+
- Reference any related issues (e.g., `Closes #123`).
|
|
5
|
+
|
|
6
|
+
# Testing
|
|
7
|
+
|
|
8
|
+
- [ ] `npm test`
|
|
9
|
+
- [ ] Other (specify):
|
|
10
|
+
|
|
11
|
+
# Documentation
|
|
12
|
+
|
|
13
|
+
- [ ] README updated
|
|
14
|
+
- [ ] Other docs updated (specify):
|
|
15
|
+
|
|
16
|
+
# Checklist
|
|
17
|
+
|
|
18
|
+
- [ ] Followed the development workflow enforced by the MCP server
|
|
19
|
+
- [ ] Added/updated tests as needed
|
|
20
|
+
- [ ] Verified single data/event/command/effect/validation/permission/authorization/error/success/warning/info flows remain intact
|
|
21
|
+
- [ ] Removed unused imports and console statements
|
|
22
|
+
- [ ] Ready for review
|