From ecbbc3ae6fd1754a096563d58d3ee7d78d777fa3 Mon Sep 17 00:00:00 2001 From: Colin McDonnell Date: Wed, 21 Jan 2026 01:18:17 +0000 Subject: [PATCH] Comment review tool --- entry | 1 - mcp/reviewComments.ts | 2 ++ modes.ts | 1 - scratch.ts | 15 --------------- 4 files changed, 2 insertions(+), 17 deletions(-) delete mode 100644 scratch.ts diff --git a/entry b/entry index fbd85e8..a5ee8da 100755 --- a/entry +++ b/entry @@ -121638,7 +121638,6 @@ function computeModes() { 3. Fetch review comments using ${ghPullfrogMcpName}/get_review_comments with \`pull_number\` and \`review_id\` from EVENT DATA. This returns \`commentsPath\` - read that file for full comment details with diff context. If EVENT DATA contains a \`triggerer\` field (indicating who requested fixes), you can pass \`approved_by\` to filter to only comments they approved with \u{1F44D}. 4. Review the feedback provided. Understand each review comment and what changes are being requested. - - **If there are no actionable comments** (e.g., the review is an approval with no specific feedback to address), do NOT post a progress comment. Simply exit without taking action. 5. If the request requires understanding the codebase structure or conventions, gather relevant context. Read AGENTS.md if it exists. diff --git a/mcp/reviewComments.ts b/mcp/reviewComments.ts index bbe10e2..5187d65 100644 --- a/mcp/reviewComments.ts +++ b/mcp/reviewComments.ts @@ -6,6 +6,8 @@ import type { ToolContext } from "./server.ts"; import { execute, tool } from "./shared.ts"; // fragment for nested replyTo (5 levels deep covers most threads) +// because in_reply_to_id generally points to the top-level comment +// this doesn't actually work as expected const REPLY_TO_FRAGMENT = ` replyTo { databaseId diff --git a/modes.ts b/modes.ts index c189aa7..dc41241 100644 --- a/modes.ts +++ b/modes.ts @@ -76,7 +76,6 @@ export function computeModes(): Mode[] { 3. Fetch review comments using ${ghPullfrogMcpName}/get_review_comments with \`pull_number\` and \`review_id\` from EVENT DATA. This returns \`commentsPath\` - read that file for full comment details with diff context. If EVENT DATA contains a \`triggerer\` field (indicating who requested fixes), you can pass \`approved_by\` to filter to only comments they approved with 👍. 4. Review the feedback provided. Understand each review comment and what changes are being requested. - - **If there are no actionable comments** (e.g., the review is an approval with no specific feedback to address), do NOT post a progress comment. Simply exit without taking action. 5. If the request requires understanding the codebase structure or conventions, gather relevant context. Read AGENTS.md if it exists. diff --git a/scratch.ts b/scratch.ts deleted file mode 100644 index 64ee81b..0000000 --- a/scratch.ts +++ /dev/null @@ -1,15 +0,0 @@ -import { spawnSync } from "child_process"; -import { existsSync } from "fs"; - -function findCliPath(name: string): string | null { - const result = spawnSync("which", [name], { encoding: "utf-8" }); - if (result.status === 0 && result.stdout) { - const cliPath = result.stdout.trim(); - if (cliPath && existsSync(cliPath)) { - return cliPath; - } - } - return null; -} - -console.log(findCliPath("codei"));