@apogeelabs/the-agency 0.6.0 → 0.7.0

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 CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@apogeelabs/the-agency",
3
- "version": "0.6.0",
3
+ "version": "0.7.0",
4
4
  "description": "Centralized Claude Code agents, commands, and workflows",
5
5
  "type": "module",
6
6
  "bin": {
@@ -223,7 +223,7 @@ Based on the changes in this PR, provide concrete testing recommendations. This
223
223
  Produce your output as inline markdown with these sections:
224
224
 
225
225
  ```markdown
226
- # PR Review: #{number} — {title}
226
+ # {title}
227
227
 
228
228
  **Branch**: {headRefName} → {baseRefName}
229
229
  **Changes**: {additions} additions, {deletions} deletions across {changedFiles} files
@@ -288,3 +288,31 @@ Each block contains:
288
288
 
289
289
  [If test coverage is already good, say so and note any minor gaps]
290
290
  ```
291
+
292
+ ## Step 9: Offer to Update PR Description
293
+
294
+ After producing the review output, ask the user:
295
+
296
+ > **Would you like to update the PR description with this review?**
297
+
298
+ If the user declines, you're done.
299
+
300
+ If the user accepts, update the PR description by prepending the review content above the original description, separated as follows:
301
+
302
+ ```
303
+ {review content}
304
+
305
+ ---
306
+ Original PR Description
307
+ ---
308
+
309
+ {original PR description}
310
+ ```
311
+
312
+ Use the `body` captured in Step 2 as the original PR description. Update the PR with:
313
+
314
+ ```bash
315
+ gh pr edit --body "{new body content}"
316
+ ```
317
+
318
+ ⚠️ **Preserve the original description exactly as-is** — no reformatting, no trimming, no "improving" it.