brain-dev 2.3.0 → 2.3.1
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.
|
@@ -237,6 +237,9 @@ function buildStepInstructions(taskNum, slug, taskDir, brainDir, mode, research,
|
|
|
237
237
|
'- Project code style consistency',
|
|
238
238
|
'- Confidence-based filtering (only real issues, ≥80%)',
|
|
239
239
|
'',
|
|
240
|
+
'MANDATORY: Do NOT skip review because changes seem "small" or "trivial".',
|
|
241
|
+
'There are ZERO valid reasons to skip this step.',
|
|
242
|
+
'',
|
|
240
243
|
'Then run: `npx brain-dev new-task --continue`'
|
|
241
244
|
].join('\n');
|
|
242
245
|
}
|
package/commands/brain/review.md
CHANGED
|
@@ -16,11 +16,18 @@ framework best practices, and project code style consistency using confidence-ba
|
|
|
16
16
|
<critical-rules>
|
|
17
17
|
PIPELINE ENFORCEMENT (NON-NEGOTIABLE):
|
|
18
18
|
1. Run `npx brain-dev review` FIRST — before reading code, before analyzing, before suggesting fixes
|
|
19
|
-
2. READ the full output — it
|
|
19
|
+
2. READ the full output — it spawns brain-reviewer agent with framework-specific expertise
|
|
20
20
|
3. FOLLOW the nextAction field — copy the exact command, do not modify it
|
|
21
21
|
4. If output shows an ERROR: follow the recovery path in the output, do NOT debug manually
|
|
22
22
|
5. If output shows a CHECKPOINT: use AskUserQuestion, do NOT pick options yourself
|
|
23
23
|
|
|
24
|
+
ZERO EXCEPTIONS — REVIEW IS ALWAYS MANDATORY:
|
|
25
|
+
- "Changes are minimal" → STILL review. Small changes cause big bugs.
|
|
26
|
+
- "Only 2 files changed" → STILL review. Every file matters.
|
|
27
|
+
- "This is trivial" → STILL review. You don't decide what's trivial, the reviewer agent does.
|
|
28
|
+
- "I can see the code is fine" → STILL review. You are not the reviewer. The pipeline is.
|
|
29
|
+
- NEVER say "skipping review" for any reason. There is no valid reason to skip.
|
|
30
|
+
|
|
24
31
|
CONSEQUENCE OF SKIPPING: Pipeline tracks state, creates audit trails, spawns specialized agents,
|
|
25
32
|
and injects framework-specific expertise. Skipping it means: no state tracking, no audit trail,
|
|
26
33
|
no specialized agents, no framework guidance, potential data loss in .brain/ state.
|
package/hooks/bootstrap.sh
CHANGED
|
@@ -89,6 +89,11 @@ try {
|
|
|
89
89
|
'6. STATE: Run /brain:progress before suggesting next steps.',
|
|
90
90
|
' For /brain:update, always use: npx brain-dev@latest update',
|
|
91
91
|
' NEVER run brain-dev init after an update.',
|
|
92
|
+
'',
|
|
93
|
+
'7. REVIEW IS MANDATORY: After execute, ALWAYS run /brain:review before /brain:verify.',
|
|
94
|
+
' NEVER skip review because changes seem "small", "trivial", or "minimal".',
|
|
95
|
+
' You do NOT decide what needs review. The reviewer agent decides.',
|
|
96
|
+
' There are ZERO valid reasons to skip the review step.',
|
|
92
97
|
'--- End Brain Context ---'
|
|
93
98
|
];
|
|
94
99
|
console.log(lines.join('\n'));
|