From 08101a0e67df765016351a3022ab98e724add063 Mon Sep 17 00:00:00 2001 From: Colin McDonnell Date: Wed, 8 Apr 2026 18:31:46 +0000 Subject: [PATCH] summarize mode: drop subagent delegation and dead effort hint the "delegate a subagent" instruction doubled LLM sessions for every summary run, and "use mini or auto effort" was a no-op since the agent always runs at high/max effort. Made-with: Cursor --- entry | 29 ++++++----------------------- mcp/selectMode.ts | 14 +++----------- modes.ts | 15 +++------------ 3 files changed, 12 insertions(+), 46 deletions(-) diff --git a/entry b/entry index 1581cfe..4c0070f 100755 --- a/entry +++ b/entry @@ -148152,17 +148152,9 @@ An existing summary comment was found for this PR. Update it rather than creatin 1. Use \`previousSummaryBody\` from this response as the current summary to revise. 2. Checkout the PR via \`${t("checkout_pr")}\` \u2014 this returns PR metadata and a \`diffPath\`. -3. Delegate a subagent with: - - the diff file path and PR metadata - - the existing summary body (\`previousSummaryBody\`) so it can update rather than rewrite from scratch - - format instructions from EVENT INSTRUCTIONS (if any) - - instruct it to produce an updated summary reflecting the current state of the PR and return it as its final response -4. After the subagent completes, call \`${t("edit_issue_comment")}\` with \`commentId: existingSummaryCommentId\` (from this response) and the updated summary body. -5. Call \`${t("report_progress")}\` with a brief note (e.g., "Updated PR summary."). - -### Effort - -Use mini or auto effort.` +3. Read the diff using the TOC to selectively read relevant sections. Produce an updated summary reflecting the current state of the PR, using the existing summary (\`previousSummaryBody\`) as a starting point. Follow format instructions from EVENT INSTRUCTIONS (if any). +4. Call \`${t("edit_issue_comment")}\` with \`commentId: existingSummaryCommentId\` (from this response) and the updated summary body. +5. Call \`${t("report_progress")}\` with a brief note (e.g., "Updated PR summary.").` }; } var modeInstructionParent = { @@ -149003,18 +148995,9 @@ ${learningsStep(t, 4)}` prompt: `### Checklist 1. Checkout the PR via \`${t("checkout_pr")}\` \u2014 this returns PR metadata and a \`diffPath\`. -2. Delegate a subagent to analyze the diff and produce a structured summary. Include in its prompt: - - the diff file path - - PR metadata (title, file count, commit count, base/head branches) - - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing - - instruct it to use the TOC to selectively read relevant diff sections, not the entire file - - instruct it to return the full summary markdown as its final response -3. After the subagent completes, call \`${t("create_issue_comment")}\` with \`type: "Summary"\` and the summary body. -4. Call \`${t("report_progress")}\` with a brief note (e.g., "Posted PR summary."). - -### Effort - -Use mini or auto effort.` +2. Read the diff using the TOC to selectively read relevant sections (not the entire file). Produce a structured summary using format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing. +3. Call \`${t("create_issue_comment")}\` with \`type: "Summary"\` and the summary body. +4. Call \`${t("report_progress")}\` with a brief note (e.g., "Posted PR summary.").` } ]; } diff --git a/mcp/selectMode.ts b/mcp/selectMode.ts index 187deba..35929eb 100644 --- a/mcp/selectMode.ts +++ b/mcp/selectMode.ts @@ -39,17 +39,9 @@ An existing summary comment was found for this PR. Update it rather than creatin 1. Use \`previousSummaryBody\` from this response as the current summary to revise. 2. Checkout the PR via \`${t("checkout_pr")}\` — this returns PR metadata and a \`diffPath\`. -3. Delegate a subagent with: - - the diff file path and PR metadata - - the existing summary body (\`previousSummaryBody\`) so it can update rather than rewrite from scratch - - format instructions from EVENT INSTRUCTIONS (if any) - - instruct it to produce an updated summary reflecting the current state of the PR and return it as its final response -4. After the subagent completes, call \`${t("edit_issue_comment")}\` with \`commentId: existingSummaryCommentId\` (from this response) and the updated summary body. -5. Call \`${t("report_progress")}\` with a brief note (e.g., "Updated PR summary."). - -### Effort - -Use mini or auto effort.`, +3. Read the diff using the TOC to selectively read relevant sections. Produce an updated summary reflecting the current state of the PR, using the existing summary (\`previousSummaryBody\`) as a starting point. Follow format instructions from EVENT INSTRUCTIONS (if any). +4. Call \`${t("edit_issue_comment")}\` with \`commentId: existingSummaryCommentId\` (from this response) and the updated summary body. +5. Call \`${t("report_progress")}\` with a brief note (e.g., "Updated PR summary.").`, }; } diff --git a/modes.ts b/modes.ts index 4089729..0d77a61 100644 --- a/modes.ts +++ b/modes.ts @@ -240,18 +240,9 @@ ${learningsStep(t, 4)}`, prompt: `### Checklist 1. Checkout the PR via \`${t("checkout_pr")}\` — this returns PR metadata and a \`diffPath\`. -2. Delegate a subagent to analyze the diff and produce a structured summary. Include in its prompt: - - the diff file path - - PR metadata (title, file count, commit count, base/head branches) - - format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing - - instruct it to use the TOC to selectively read relevant diff sections, not the entire file - - instruct it to return the full summary markdown as its final response -3. After the subagent completes, call \`${t("create_issue_comment")}\` with \`type: "Summary"\` and the summary body. -4. Call \`${t("report_progress")}\` with a brief note (e.g., "Posted PR summary."). - -### Effort - -Use mini or auto effort.`, +2. Read the diff using the TOC to selectively read relevant sections (not the entire file). Produce a structured summary using format instructions from EVENT INSTRUCTIONS (if any); otherwise use default format: TL;DR, key changes list, per-change sections with plain-language \`##\` titles and before/after framing. +3. Call \`${t("create_issue_comment")}\` with \`type: "Summary"\` and the summary body. +4. Call \`${t("report_progress")}\` with a brief note (e.g., "Posted PR summary.").`, }, ]; }