wogiflow 1.0.42 → 1.0.43
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/scripts/flow-bug.js +109 -17
- package/templates/bug-report.md +113 -20
package/package.json
CHANGED
package/scripts/flow-bug.js
CHANGED
|
@@ -77,7 +77,7 @@ function createBugContent(bug) {
|
|
|
77
77
|
|
|
78
78
|
const date = createdAt.split('T')[0];
|
|
79
79
|
const discoveredSection = discoveredFrom
|
|
80
|
-
? `**Discovered From**: ${discoveredFrom}\n**Discovered During**: ${discoveredDuring}\n`
|
|
80
|
+
? `**Discovered From**: ${discoveredFrom}\n**Discovered During**: ${discoveredDuring || 'implementation'}\n`
|
|
81
81
|
: '';
|
|
82
82
|
|
|
83
83
|
return `# ${id}: ${title}
|
|
@@ -88,30 +88,120 @@ function createBugContent(bug) {
|
|
|
88
88
|
**Priority**: ${priority}
|
|
89
89
|
**Tags**: #bug
|
|
90
90
|
${discoveredSection}
|
|
91
|
-
##
|
|
92
|
-
[
|
|
91
|
+
## Bug Summary
|
|
92
|
+
[1-2 sentences: What is broken and what is the impact?]
|
|
93
93
|
|
|
94
|
-
##
|
|
94
|
+
## Reproduction
|
|
95
|
+
|
|
96
|
+
### Steps to Reproduce
|
|
95
97
|
1. [Step 1]
|
|
96
98
|
2. [Step 2]
|
|
97
99
|
3. [Step 3]
|
|
98
100
|
|
|
99
|
-
|
|
101
|
+
### Expected Behavior
|
|
100
102
|
[What should happen]
|
|
101
103
|
|
|
102
|
-
|
|
104
|
+
### Actual Behavior
|
|
103
105
|
[What actually happens]
|
|
104
106
|
|
|
105
|
-
|
|
106
|
-
- Browser:
|
|
107
|
-
- OS:
|
|
108
|
-
- Version:
|
|
107
|
+
### Environment
|
|
108
|
+
- Browser: [if applicable]
|
|
109
|
+
- OS: [if applicable]
|
|
110
|
+
- Version: [app version]
|
|
111
|
+
- Node/Runtime: [if applicable]
|
|
112
|
+
|
|
113
|
+
### Screenshots/Logs
|
|
114
|
+
[Attach screenshots, error logs, or stack traces]
|
|
115
|
+
|
|
116
|
+
---
|
|
117
|
+
|
|
118
|
+
## Root Cause Analysis
|
|
119
|
+
|
|
120
|
+
### What Went Wrong?
|
|
121
|
+
[Technical explanation of the bug - what part of the code/logic is failing and why]
|
|
122
|
+
|
|
123
|
+
### Why Did This Happen?
|
|
124
|
+
[Choose one or more]
|
|
125
|
+
- [ ] Logic error in implementation
|
|
126
|
+
- [ ] Missing edge case handling
|
|
127
|
+
- [ ] Incorrect assumption about inputs/state
|
|
128
|
+
- [ ] Race condition / timing issue
|
|
129
|
+
- [ ] External dependency failure
|
|
130
|
+
- [ ] Configuration/environment issue
|
|
131
|
+
- [ ] Prompt/instruction unclear or ambiguous
|
|
132
|
+
- [ ] Other: [explain]
|
|
133
|
+
|
|
134
|
+
### Source of the Problem
|
|
135
|
+
<!-- For AI-assisted development, this helps us learn -->
|
|
136
|
+
- **Prompt issue**: [Was the original request ambiguous or missing context?]
|
|
137
|
+
- **Logic gap**: [What reasoning led to the bug?]
|
|
138
|
+
- **Missing context**: [What information would have prevented this?]
|
|
139
|
+
|
|
140
|
+
---
|
|
141
|
+
|
|
142
|
+
## Fix Approaches
|
|
143
|
+
|
|
144
|
+
### Approach 1: [Name] (Recommended)
|
|
145
|
+
**Description**: [How this approach fixes the bug]
|
|
146
|
+
**Pros**: [Benefits]
|
|
147
|
+
**Cons**: [Drawbacks]
|
|
148
|
+
**Files affected**: [List files]
|
|
149
|
+
|
|
150
|
+
### Approach 2: [Name] (Alternative)
|
|
151
|
+
**Description**: [How this approach fixes the bug]
|
|
152
|
+
**Pros**: [Benefits]
|
|
153
|
+
**Cons**: [Drawbacks]
|
|
154
|
+
**Files affected**: [List files]
|
|
155
|
+
|
|
156
|
+
### Chosen Approach
|
|
157
|
+
[Which approach and why]
|
|
158
|
+
|
|
159
|
+
---
|
|
160
|
+
|
|
161
|
+
## Acceptance Criteria
|
|
162
|
+
|
|
163
|
+
### Scenario 1: Bug is fixed
|
|
164
|
+
**Given** [the conditions that previously triggered the bug]
|
|
165
|
+
**When** [the action that caused the bug]
|
|
166
|
+
**Then** [the expected correct behavior]
|
|
167
|
+
|
|
168
|
+
### Scenario 2: No regression
|
|
169
|
+
**Given** [related functionality]
|
|
170
|
+
**When** [normal usage]
|
|
171
|
+
**Then** [existing behavior is preserved]
|
|
172
|
+
|
|
173
|
+
### Scenario 3: Edge case handling
|
|
174
|
+
**Given** [edge case conditions]
|
|
175
|
+
**When** [edge case action]
|
|
176
|
+
**Then** [graceful handling]
|
|
177
|
+
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
## Test Strategy
|
|
181
|
+
- [ ] Unit test: [What to test]
|
|
182
|
+
- [ ] Integration test: [What to test]
|
|
183
|
+
- [ ] Manual verification: [Steps to verify fix]
|
|
184
|
+
|
|
185
|
+
## Verification Checklist
|
|
186
|
+
<!-- Quick steps to confirm the bug is fixed -->
|
|
187
|
+
1. [ ] [Step to verify the bug no longer occurs]
|
|
188
|
+
2. [ ] [Step to verify no regression]
|
|
189
|
+
3. [ ] [Step to verify edge cases]
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
193
|
+
## Prevention & Learning
|
|
194
|
+
|
|
195
|
+
### How to Prevent Similar Bugs
|
|
196
|
+
[What changes to process, prompts, or code patterns would prevent this?]
|
|
109
197
|
|
|
110
|
-
|
|
111
|
-
|
|
198
|
+
### Learnings to Capture
|
|
199
|
+
<!-- These should be added to decisions.md or skill learnings -->
|
|
200
|
+
- [ ] Pattern to add to decisions.md: [describe]
|
|
201
|
+
- [ ] Skill learning to record: [describe]
|
|
202
|
+
- [ ] Prompt improvement: [describe]
|
|
112
203
|
|
|
113
|
-
|
|
114
|
-
[If you have ideas about what's causing it or how to fix]
|
|
204
|
+
---
|
|
115
205
|
|
|
116
206
|
## Related
|
|
117
207
|
- [Related request-log entries]
|
|
@@ -119,9 +209,11 @@ ${discoveredSection}
|
|
|
119
209
|
${discoveredFrom ? `- Discovered while working on: ${discoveredFrom}` : ''}
|
|
120
210
|
|
|
121
211
|
## Resolution
|
|
122
|
-
|
|
123
|
-
- Fixed in
|
|
124
|
-
- Root cause
|
|
212
|
+
<!-- Fill in when fixed -->
|
|
213
|
+
- **Fixed in**: [commit hash or PR]
|
|
214
|
+
- **Root cause confirmed**: [yes/no - was initial analysis correct?]
|
|
215
|
+
- **Learnings applied**: [what was added to decisions.md/skills?]
|
|
216
|
+
- **Tests added**: [what tests were added?]
|
|
125
217
|
`;
|
|
126
218
|
}
|
|
127
219
|
|
package/templates/bug-report.md
CHANGED
|
@@ -1,43 +1,136 @@
|
|
|
1
|
-
# wf-XXXXXXXX
|
|
1
|
+
# [wf-XXXXXXXX] [Title]
|
|
2
2
|
|
|
3
3
|
**Created**: [date]
|
|
4
|
-
**Status**: Open
|
|
5
|
-
**Severity**: Critical
|
|
4
|
+
**Status**: Open | In Progress | Fixed | Closed
|
|
5
|
+
**Severity**: Critical | High | Medium | Low
|
|
6
6
|
**Priority**: P0-P4
|
|
7
7
|
**Tags**: #bug #component:[name] #screen:[name]
|
|
8
8
|
**Discovered From**: [wf-XXXXXXXX or empty if not during task]
|
|
9
|
-
**Discovered During**: implementation
|
|
9
|
+
**Discovered During**: implementation | testing | review | production
|
|
10
10
|
|
|
11
|
-
##
|
|
12
|
-
[
|
|
11
|
+
## Bug Summary
|
|
12
|
+
[1-2 sentences: What is broken and what is the impact?]
|
|
13
13
|
|
|
14
|
-
##
|
|
14
|
+
## Reproduction
|
|
15
|
+
|
|
16
|
+
### Steps to Reproduce
|
|
15
17
|
1. [Step 1]
|
|
16
18
|
2. [Step 2]
|
|
17
19
|
3. [Step 3]
|
|
18
20
|
|
|
19
|
-
|
|
21
|
+
### Expected Behavior
|
|
20
22
|
[What should happen]
|
|
21
23
|
|
|
22
|
-
|
|
24
|
+
### Actual Behavior
|
|
23
25
|
[What actually happens]
|
|
24
26
|
|
|
25
|
-
|
|
26
|
-
- Browser:
|
|
27
|
-
- OS:
|
|
28
|
-
- Version:
|
|
27
|
+
### Environment
|
|
28
|
+
- Browser: [if applicable]
|
|
29
|
+
- OS: [if applicable]
|
|
30
|
+
- Version: [app version]
|
|
31
|
+
- Node/Runtime: [if applicable]
|
|
32
|
+
|
|
33
|
+
### Screenshots/Logs
|
|
34
|
+
[Attach screenshots, error logs, or stack traces]
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
## Root Cause Analysis
|
|
39
|
+
|
|
40
|
+
### What Went Wrong?
|
|
41
|
+
[Technical explanation of the bug - what part of the code/logic is failing and why]
|
|
42
|
+
|
|
43
|
+
### Why Did This Happen?
|
|
44
|
+
[Choose one or more]
|
|
45
|
+
- [ ] Logic error in implementation
|
|
46
|
+
- [ ] Missing edge case handling
|
|
47
|
+
- [ ] Incorrect assumption about inputs/state
|
|
48
|
+
- [ ] Race condition / timing issue
|
|
49
|
+
- [ ] External dependency failure
|
|
50
|
+
- [ ] Configuration/environment issue
|
|
51
|
+
- [ ] Prompt/instruction unclear or ambiguous
|
|
52
|
+
- [ ] Other: [explain]
|
|
53
|
+
|
|
54
|
+
### Source of the Problem
|
|
55
|
+
<!-- For AI-assisted development, this helps us learn -->
|
|
56
|
+
- **Prompt issue**: [Was the original request ambiguous or missing context?]
|
|
57
|
+
- **Logic gap**: [What reasoning led to the bug?]
|
|
58
|
+
- **Missing context**: [What information would have prevented this?]
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## Fix Approaches
|
|
63
|
+
|
|
64
|
+
### Approach 1: [Name] (Recommended)
|
|
65
|
+
**Description**: [How this approach fixes the bug]
|
|
66
|
+
**Pros**: [Benefits]
|
|
67
|
+
**Cons**: [Drawbacks]
|
|
68
|
+
**Files affected**: [List files]
|
|
69
|
+
|
|
70
|
+
### Approach 2: [Name] (Alternative)
|
|
71
|
+
**Description**: [How this approach fixes the bug]
|
|
72
|
+
**Pros**: [Benefits]
|
|
73
|
+
**Cons**: [Drawbacks]
|
|
74
|
+
**Files affected**: [List files]
|
|
75
|
+
|
|
76
|
+
### Chosen Approach
|
|
77
|
+
[Which approach and why]
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## Acceptance Criteria
|
|
82
|
+
|
|
83
|
+
### Scenario 1: Bug is fixed
|
|
84
|
+
**Given** [the conditions that previously triggered the bug]
|
|
85
|
+
**When** [the action that caused the bug]
|
|
86
|
+
**Then** [the expected correct behavior]
|
|
87
|
+
|
|
88
|
+
### Scenario 2: No regression
|
|
89
|
+
**Given** [related functionality]
|
|
90
|
+
**When** [normal usage]
|
|
91
|
+
**Then** [existing behavior is preserved]
|
|
92
|
+
|
|
93
|
+
### Scenario 3: Edge case handling
|
|
94
|
+
**Given** [edge case conditions]
|
|
95
|
+
**When** [edge case action]
|
|
96
|
+
**Then** [graceful handling]
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## Test Strategy
|
|
101
|
+
- [ ] Unit test: [What to test]
|
|
102
|
+
- [ ] Integration test: [What to test]
|
|
103
|
+
- [ ] Manual verification: [Steps to verify fix]
|
|
104
|
+
|
|
105
|
+
## Verification Checklist
|
|
106
|
+
<!-- Quick steps to confirm the bug is fixed -->
|
|
107
|
+
1. [ ] [Step to verify the bug no longer occurs]
|
|
108
|
+
2. [ ] [Step to verify no regression]
|
|
109
|
+
3. [ ] [Step to verify edge cases]
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Prevention & Learning
|
|
114
|
+
|
|
115
|
+
### How to Prevent Similar Bugs
|
|
116
|
+
[What changes to process, prompts, or code patterns would prevent this?]
|
|
29
117
|
|
|
30
|
-
|
|
31
|
-
|
|
118
|
+
### Learnings to Capture
|
|
119
|
+
<!-- These should be added to decisions.md or skill learnings -->
|
|
120
|
+
- [ ] Pattern to add to decisions.md: [describe]
|
|
121
|
+
- [ ] Skill learning to record: [describe]
|
|
122
|
+
- [ ] Prompt improvement: [describe]
|
|
32
123
|
|
|
33
|
-
|
|
34
|
-
[If you have ideas about what's causing it or how to fix]
|
|
124
|
+
---
|
|
35
125
|
|
|
36
126
|
## Related
|
|
37
127
|
- [Related request-log entries]
|
|
38
128
|
- [Related components from app-map]
|
|
129
|
+
- [Related tasks/stories]
|
|
39
130
|
|
|
40
131
|
## Resolution
|
|
41
|
-
|
|
42
|
-
- Fixed in
|
|
43
|
-
- Root cause
|
|
132
|
+
<!-- Fill in when fixed -->
|
|
133
|
+
- **Fixed in**: [commit hash or PR]
|
|
134
|
+
- **Root cause confirmed**: [yes/no - was initial analysis correct?]
|
|
135
|
+
- **Learnings applied**: [what was added to decisions.md/skills?]
|
|
136
|
+
- **Tests added**: [what tests were added?]
|