You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parent task MUST create this file (and .roo/tmp/release-notes/temp_pr_inclusion_v[version].json, .roo/tmp/release-notes/temp_pr_list_v[VERSION].md if needed) before ANY subtasks.
114
-
Subtasks will ONLY add entries to these temp files using the available safe file-editing capability (preserve existing content; no overwrites).
115
-
Parent task MUST NOT add entries to temp_pr_analysis_v[version].md; this file is reserved exclusively for subtask outputs. The parent may only create/initialize the empty file(s).
116
-
Temp files live under .roo/tmp/release-notes/
119
+
Create the temp directory and file to track PR analysis results.
120
+
Each PR analysis will be appended to this file as it completes.
117
121
</details>
118
122
</initialization>
119
123
120
-
<subtask_patternpriority="CRITICAL">
124
+
<inline_analysis_workflow>
121
125
<for_each>PR in list</for_each>
122
-
<action>Create investigation subtask using new_task tool</action>
123
-
<implementation>
124
-
<tool>new_task</tool>
125
-
<mode>release-notes-writer</mode>
126
-
<description>
127
-
For each PR in the fetched or provided list, create a separate subtask
128
-
using the new_task tool. Each subtask investigates one PR independently.
129
-
</description>
130
-
<iteration_approach>
131
-
Process PRs sequentially or in batches, creating a new_task for each PR number.
132
-
Wait for all subtasks to complete before proceeding to compilation phase.
133
-
</iteration_approach>
134
-
</implementation>
135
-
<message_template>
136
-
Investigate PR #[number] for release notes v[version].
5. Identify documentation needs (new features, behavior changes, deprecations)
142
-
6. Add to .roo/tmp/release-notes/temp_pr_analysis_v[version].md at the start, preserving existing content (use the available safe file-editing capability)
143
-
144
-
Include documentation flags:
145
-
- docs-new: Completely new feature
146
-
- docs-update: Existing docs need updating
147
-
- docs-example: New examples needed
148
-
- docs-migration: Breaking changes
149
-
150
-
CRITICAL: Never overwrite existing content; only add entries while preserving prior content.
151
-
MANDATORY: Insert the marker line '<!-- generated-by-subtask: true -->' immediately before the '---' separator in each PR entry.
Categorize the change and identify documentation needs
190
-
Add analysis to .roo/tmp/release-notes/temp_pr_analysis_v3.20.1.md at the start, preserving existing content</message>
191
-
<todos>
192
-
[ ] Fetch PR #1234 details
193
-
[ ] Extract linked issues and get details
194
-
[ ] Categorize and analyze
195
-
[ ] Write to temp_pr_analysis_v3.20.1.md
196
-
</todos>
197
-
</new_task>
198
-
]]></implementation>
199
-
<critical_notes>
200
-
- Parent creates temp files first
201
-
- Each PR gets its own subtask
202
-
- Subtasks only add entries; never overwrite existing content
203
-
</critical_notes>
204
-
</subtask_creation_example>
179
+
<processing_guidance>
180
+
<note>Process PRs sequentially, appending each analysis to the tracking file</note>
181
+
<note>For large PR lists (10+), provide progress updates every 5 PRs</note>
182
+
<note>If a PR fetch fails, note the error and continue with remaining PRs</note>
183
+
</processing_guidance>
205
184
</phase>
206
185
207
186
<phasename="changelog_alignment">
@@ -341,11 +320,11 @@ fi
341
320
- Author signal: if bullet contains "thanks @user", "by @user", or "PR by @user" and that user equals the PR author or credited issue reporter, add +0.20 to score
342
321
- Keyword boost: +0.05 when provider/model/domain keywords (e.g., OpenAI, Claude, Grok, Chutes, Qwen, LongCat, etc.) appear in both
- 0.45 <= score < 0.65 OR multiple candidates within 0.05 -> ambiguous (needs review)
325
+
- score < 0.45 -> unlinked
347
326
Tie-breakers: higher score; if within 0.02 then same author; then closer merge date to release date; then lowest PR number
348
-
Edge case: If bullet credits exactly one username and exactly one PR in the window has that author, accept with score >= 0.50 (confidence="author-boost")
327
+
Edge case: If bullet credits exactly one username and exactly one PR in the window has that author, accept with score >= 0.50 (confidence="author-boost")
349
328
Implementation notes:
350
329
- Match only against PRs fetched for the version's date window
351
330
- Persist mapping bullet_text -> { prNumber, confidenceScore, rationaleSignals[] } and use it to compute linked/ambiguous/unlinked counts
@@ -354,33 +333,24 @@ fi
354
333
</step>
355
334
356
335
<stepnumber="2a">
357
-
<action>Supplement candidate PR set with changelog-referenced PRs not in fetched list and spawn analysis subtasks</action>
336
+
<action>Supplement candidate PR set with changelog-referenced PRs not in fetched list</action>
358
337
<details>
359
338
- Identify referenced PR numbers from step 2 that are missing from .roo/tmp/release-notes/temp_pr_analysis_v[version].md
360
-
- For each missing PR, fetch details and create a new investigation subtask (same pattern as pr_processing) to add analysis to temp_pr_analysis_v[version].md without overwriting existing content
339
+
- For each missing PR, fetch details and analyze inline (same process as pr_processing phase)
361
340
- Mark these as out_of_range if their mergedAt is outside the computed date window
362
-
- Wait for all spawned subtasks to complete before proceeding
341
+
- Append analysis to the tracking file
363
342
</details>
364
-
<commands>
365
-
<fetch><![CDATA[
366
-
# For each referenced PR number N not present in .roo/tmp/release-notes/temp_pr_analysis_v[version].md:
367
-
gh pr view N --repo RooCodeInc/Roo-Code --json number,title,author,mergedAt,labels,files
368
-
]]></fetch>
369
-
<spawn_subtask><![CDATA[
370
-
<new_task>
371
-
<mode>release-notes-writer</mode>
372
-
<message>Investigate PR #[NUMBER] (changelog-referenced, possibly out of original range) for release notes v[version]. Follow standard analysis and add to .roo/tmp/release-notes/temp_pr_analysis_v[version].md without overwriting existing content.</message>
- Inclusion policy required: If .roo/tmp/release-notes/temp_pr_inclusion_v[version].json does not exist, you MUST execute the changelog_alignment phase now to obtain an inclusion decision, then retry this step.
462
-
- Subtask provenance required: All PR analysis entries MUST contain the marker '<!-- generated-by-subtask: true -->'. If any entries are missing this marker, HALT and re-run PR analysis via per-PR subtasks before proceeding.
463
432
</precondition>
464
433
<filtering>
465
434
Include only PRs listed in "included" from .roo/tmp/release-notes/temp_pr_inclusion_v[version].json. Do not fall back to using all analyzed PRs without an explicit inclusion policy.
<when>If any documentation flags were identified during PR analysis</when>
530
+
<output>
531
+
Present a summary of documentation needs to the user:
532
+
- List items flagged as docs-new (new features needing new pages)
533
+
- List items flagged as docs-update (existing pages needing updates)
534
+
- List items flagged as docs-example (new examples needed)
535
+
- List items flagged as docs-migration (migration guides needed)
536
+
537
+
The user can then follow up with documentation-writer mode separately if desired.
538
+
</output>
539
+
<template><![CDATA[
540
+
**Documentation Update Summary:**
541
+
542
+
The following items may need documentation updates:
543
+
544
+
**New Documentation Needed:**
545
+
- [Feature name]: [Brief description of what needs documenting]
546
+
547
+
**Existing Docs Updates:**
548
+
- [Page/feature]: [What needs updating]
549
+
550
+
**Examples Needed:**
551
+
- [Feature]: [Example scenarios to add]
552
+
553
+
**Migration Guides:**
554
+
- [Breaking change]: [Migration path to document]
555
+
556
+
To create these documentation updates, you can start a new task with documentation-writer mode.
557
+
]]></template>
562
558
</step>
559
+
563
560
<stepnumber="7">
564
561
<action>Cleanup temporary files</action>
565
562
<details>Delete .roo/tmp/release-notes/* (temp_pr_analysis_v[version].md, temp_pr_list_v[version].md, temp_pr_inclusion_v[version].json) after notes are finalized.</details>
@@ -700,20 +697,13 @@ gh pr list --repo RooCodeInc/Roo-Code --state merged --base main --limit 1000 \
700
697
Date format is YYYY-MM-DD (ISO 8601) where MM is month (01-12)
For each PR, the parent MUST create a subtask via new_task. The parent MUST NOT write PR analysis entries; only subtasks may add entries to .roo/tmp/release-notes/temp_pr_analysis_v[version].md without overwriting existing content. Do not proceed to changelog_alignment or compilation until all PR subtasks complete.
707
-
Even when the parent already has the PR number, title, description, or a user‑provided
708
-
summary list, it MUST still create and wait on the per‑PR subtask. These summaries are
709
-
insufficient for functional understanding of the change, discovery of linked issues, and
710
-
correct contributor attribution (PR authors and issue reporters).
700
+
All PR analysis happens inline within this task - do not spawn subtasks
711
701
</rule>
712
702
<rulepriority="CRITICAL">
713
703
Use the simplified PR extraction command for consistent results
714
704
</rule>
715
705
<rulepriority="HIGH">
716
-
Acknowledge PR author AND issue reporter, unless the username is on the release-notes “thank you” exclusion list.
706
+
Acknowledge PR author AND issue reporter, unless the username is on the release-notes "thank you" exclusion list.
717
707
If all candidate acknowledgements are excluded, omit the thanks parenthetical entirely.
0 commit comments