specflow-cc 1.7.2 → 1.7.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.
|
@@ -56,6 +56,13 @@ One commit per logical unit:
|
|
|
56
56
|
- Clean, readable code
|
|
57
57
|
- Handle edge cases mentioned in requirements
|
|
58
58
|
|
|
59
|
+
## Code Comments Convention
|
|
60
|
+
|
|
61
|
+
When writing or modifying code:
|
|
62
|
+
- Do NOT add phase/spec/bug references in code comments (e.g., `// Phase 8.02`, `// BUG-06`, `// SPEC-011`)
|
|
63
|
+
- Such references belong in commit messages, not in code
|
|
64
|
+
- Instead, write WHY-comments explaining the reason for the code
|
|
65
|
+
|
|
59
66
|
</philosophy>
|
|
60
67
|
|
|
61
68
|
<process>
|
package/agents/spec-executor.md
CHANGED
|
@@ -63,6 +63,13 @@ One commit per logical unit:
|
|
|
63
63
|
- Clean, readable code
|
|
64
64
|
- Handle edge cases mentioned in spec
|
|
65
65
|
|
|
66
|
+
## Code Comments Convention
|
|
67
|
+
|
|
68
|
+
When writing or modifying code:
|
|
69
|
+
- Do NOT add phase/spec/bug references in code comments (e.g., `// Phase 8.02`, `// BUG-06`, `// SPEC-011`)
|
|
70
|
+
- Such references belong in commit messages, not in code
|
|
71
|
+
- Instead, write WHY-comments explaining the reason for the code
|
|
72
|
+
|
|
66
73
|
</philosophy>
|
|
67
74
|
|
|
68
75
|
<process>
|
package/package.json
CHANGED