@mechanai/deepreview 2.6.1 → 2.6.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.
|
@@ -134,7 +134,19 @@ Task — Use the Task tool with subagent_type="general":
|
|
|
134
134
|
|
|
135
135
|
## Prior Findings (already reported — do not re-report or verify)
|
|
136
136
|
|
|
137
|
-
|
|
137
|
+
For each finding, include the title, category, location, AND a 1-sentence mechanism description explaining what the underlying problem is:
|
|
138
|
+
|
|
139
|
+
- [Short Issue Title] ([category]) — [file:line] — [1-sentence description of the underlying mechanism/problem]
|
|
140
|
+
|
|
141
|
+
Example:
|
|
142
|
+
|
|
143
|
+
- Missing semaphore guard (architecture) — src/module.rs:245 — concurrent operations share mutable state without synchronization
|
|
144
|
+
|
|
145
|
+
## Known Issue Locations (same file:line = likely same issue — justify if reporting again)
|
|
146
|
+
|
|
147
|
+
List every file:line from Prior Findings in a condensed location-first index:
|
|
148
|
+
|
|
149
|
+
- [file:line] — [condensed mechanism] ([category])
|
|
138
150
|
|
|
139
151
|
## Applied Fixes (changes made by previous iterations — new bugs here are regressions)
|
|
140
152
|
|
|
@@ -144,7 +156,7 @@ Task — Use the Task tool with subagent_type="general":
|
|
|
144
156
|
|
|
145
157
|
- [file:line-range] (pad each finding's file:line by 20 lines in each direction)
|
|
146
158
|
|
|
147
|
-
Deduplicate findings that appear in multiple syntheses. Return ONLY these
|
|
159
|
+
Deduplicate findings that appear in multiple syntheses. Return ONLY these four sections, nothing else."
|
|
148
160
|
|
|
149
161
|
Set PRIOR_CONTEXT to the returned text. Validate that it contains "## Prior Findings" — if not, warn the user ("Helper returned malformed prior context — proceeding without deduplication") and set PRIOR_CONTEXT="". If CONTEXT_FILE exists, prepend:
|
|
150
162
|
"## Design Decisions (intentional — do not flag)\nThe following are deliberate design choices. Do NOT flag these as issues or suggest alternatives.\n`\n" + contents of CONTEXT_FILE + "\n`\n\n"
|
|
@@ -155,7 +167,14 @@ Stage 1 — DISPATCH 5 PARALLEL REVIEWERS:
|
|
|
155
167
|
Each reviewer prompt MUST include PRIOR_CONTEXT and the novelty-seeking framing below.
|
|
156
168
|
|
|
157
169
|
The REVIEWER_PREAMBLE for all iter2+ reviewers is:
|
|
158
|
-
"Your goal is to find issues that PREVIOUS reviewers missed. Do NOT re-report, verify, or comment on prior findings.
|
|
170
|
+
"Your goal is to find issues that PREVIOUS reviewers missed. Do NOT re-report, verify, or comment on prior findings.
|
|
171
|
+
|
|
172
|
+
When you encounter a potential issue:
|
|
173
|
+
|
|
174
|
+
1. Check "Known Issue Locations" — if your finding is at or near a listed location, it is almost certainly already reported. Only report it if the mechanism is genuinely different (not just differently worded).
|
|
175
|
+
2. Check "Prior Findings" — if your finding matches an existing mechanism description (even at a different location), it is a variant of an already-reported issue. Do not report it.
|
|
176
|
+
|
|
177
|
+
If you find a bug in code listed under 'Applied Fixes', flag it as a regression.
|
|
159
178
|
|
|
160
179
|
$PRIOR_CONTEXT
|
|
161
180
|
|
|
@@ -94,7 +94,19 @@ Task — Use the Task tool with subagent_type="general":
|
|
|
94
94
|
|
|
95
95
|
## Prior Findings (already reported — do not re-report or verify)
|
|
96
96
|
|
|
97
|
-
|
|
97
|
+
For each finding, include the title, category, location, AND a 1-sentence mechanism description explaining what the underlying problem is:
|
|
98
|
+
|
|
99
|
+
- [Short Issue Title] ([category]) — [file:line or section reference] — [1-sentence description of the underlying mechanism/problem]
|
|
100
|
+
|
|
101
|
+
Example:
|
|
102
|
+
|
|
103
|
+
- Missing error recovery path (completeness) — spec.md:§3.2 — no defined behavior when upstream service returns partial data
|
|
104
|
+
|
|
105
|
+
## Known Issue Locations (same location = likely same issue — justify if reporting again)
|
|
106
|
+
|
|
107
|
+
List every location from Prior Findings in a condensed location-first index:
|
|
108
|
+
|
|
109
|
+
- [file:line or section reference] — [condensed mechanism] ([category])
|
|
98
110
|
|
|
99
111
|
## Applied Fixes (changes made by previous iterations — new bugs here are regressions)
|
|
100
112
|
|
|
@@ -104,7 +116,7 @@ Task — Use the Task tool with subagent_type="general":
|
|
|
104
116
|
|
|
105
117
|
- [file or section references, padded generously around each finding location]
|
|
106
118
|
|
|
107
|
-
Deduplicate findings that appear in multiple syntheses. Return ONLY these
|
|
119
|
+
Deduplicate findings that appear in multiple syntheses. Return ONLY these four sections, nothing else."
|
|
108
120
|
|
|
109
121
|
Set PRIOR_CONTEXT to the returned text. Validate that it contains "## Prior Findings" — if not, warn the user ("Helper returned malformed prior context — proceeding without deduplication") and set PRIOR_CONTEXT="". If CONTEXT_FILE exists, prepend:
|
|
110
122
|
"## Design Decisions (intentional — do not flag)\nThe following are deliberate design choices. Do NOT flag these as issues or suggest alternatives.\n`\n" + contents of CONTEXT_FILE + "\n`\n\n"
|
|
@@ -112,6 +124,11 @@ Set PRIOR_CONTEXT to the returned text. Validate that it contains "## Prior Find
|
|
|
112
124
|
The REVIEWER_PREAMBLE for all iter2+ reviewers is:
|
|
113
125
|
"Your goal is to find issues that PREVIOUS reviewers missed. Do NOT re-report, verify, or comment on prior findings.
|
|
114
126
|
|
|
127
|
+
When you encounter a potential issue:
|
|
128
|
+
|
|
129
|
+
1. Check "Known Issue Locations" — if your finding is at or near a listed location, it is almost certainly already reported. Only report it if the mechanism is genuinely different (not just differently worded).
|
|
130
|
+
2. Check "Prior Findings" — if your finding matches an existing mechanism description (even at a different location), it is a variant of an already-reported issue. Do not report it.
|
|
131
|
+
|
|
115
132
|
$PRIOR_CONTEXT
|
|
116
133
|
|
|
117
134
|
Find genuinely new issues. You may find different issues in covered regions, but prioritize areas not yet examined. Focus ONLY on objective issues — do NOT flag stylistic preferences."
|