tmb_comment-triage git:20261019.3444f14A

Immutable. This exact content never changes and is served at /api/v1/blob/14186b1f554b104f.

---
name: tmb_comment-triage
description: Bro's PR/MR comment triage — resolve the PR, fetch the comment threads, judge which are task-worthy, and dispatch SWE per ratified group. Loaded by bro when /monitor surfaces PR/MR comments.
allowed-tools: Task, AskUserQuestion, mcp__plugin_tmb_trajectory-server
---

# PR/MR comment triage

`pr_monitor_comments_get` does the deterministic fetch + since-marker bookkeeping. This skill is the judgment around what's task-worthy.

## Resolve the PR

If the Human named a PR number, use it. Otherwise, with `<branch>` the task's `branch_id` and `<slug>` the `owner/name` from `git -C <repo path> remote get-url origin` (`<repo path>` from `repos_list`):
- GitHub: `gh pr view <branch> -R <slug> --json number`
- GitLab: `glab mr list -R <slug> --source-branch <branch> --json`

Empty result → ask the Human which PR/MR number to monitor (free-text answer).

## Fetch

Call `pr_monitor_comments_get` with the PR number.

Carrier: resolve the linked issue with `branch_report_md` for the PR's head branch (or the task's `branch_id`), not the current checkout, rather than reading the DB directly. If unresolved, ask the Human which issue the PR is linked to (free-text answer).

## Triage (judgment)

Skip as informational when:
- The body is a bare acknowledgment — an LGTM, a +1, a thanks, a nit.
- The author is a bot (already classified by the MCP tool).
- The comment is already resolved.

Treat as task-worthy when the comment names a concrete change request (`should be`, `please change`, `consider X over Y`, ends with `?`), or contains a code suggestion fence.

Group task-worthy comments by file or shared concept; one task per group. Flag tasks that touch DB schema files (e.g. `schema/*.sql`), public API surfaces, or config directories (e.g. `agents/`, `skills/`, plugin manifest files) as `(arch-impact)`.

## Dispatch

Offer the ratified groups as a multi-select — one option per group, titled by the task it would become (suffix arch-impact ones) — and let the Human pick a subset.

For each ratified group: `task_create_batch(...)`, spawn SWE, and if arch-impact, invoke `scan_run(source='bro_auto_post_change')` after SWE returns to refresh the world model.