Skip to content

pm-dispatch: a governed PR at ACCEPT gets needs-user-decision and a Chinese 「维护者速读」 brief (what / why / risk / recommendation / the one act asked), so the maintainer can tell from the list what awaits him and confirm quickly #15894

Description

@claude

Filed by the domain:skills seat (session session_019RfFHiRCSs3JXLK4cwcfox, os-steve) on the maintainer's instruction, 2026-09-05T13:1xZ, verbatim: 「我看到有很多5小时之前积压的pr,单我从列表看不出来哪些是需要我审核的,对于需要我审核的任务,比如adr,应该由契约复审先帮我审核,用中文从业务角度写上分析和意见,然后我就可以快速确认。」 Self-triaged priority:p2, pm:queue, governed (.claude/skills/pm-dispatch/SKILL.md + scripts/pm/ensure-pm-labels.sh).

The gap

A governed PR (ADR, agent constitution, PM protocol, hooks) reaches its terminal when the seat posts ACCEPT and requests the human approvers; from the PR list nothing distinguishes it from any other open PR, and the ACCEPT is an English engineering record, not a decision brief. Today five such PRs sat between 5 and 10 hours at that terminal. Decision cards (needs-user-decision) have the list-view signal but their four-facet analysis is written for the seat, not for a quick confirmation.

What was done at once (2026-09-05T13:2xZ, no protocol text yet)

needs-user-decision applied to PR #15856, PR #15641 and objectui PR #7686; a Chinese 「维护者速读」 comment posted on each (改了什么 / 为什么改 / 风险与代价 / 席位意见 / 你要做的), and on the two decision cards #15453 and #15647.

What this card writes (the rule, once, in the file that governs the seat)

  1. SKILL.md 入队与落地 (the governed endgame): at ACCEPT on a governed PR the seat, in the same stroke, (a) adds needs-user-decision to the PR and (b) posts a Chinese 「维护者速读」 comment in the fixed five-part shape — what changed in business terms, why, risk and cost (with the rollback), the seat's recommendation, and the one act asked of the maintainer. The English verdict stays the review record; the 速读 is the maintainer's brief. The label leaves with the merge (a closed PR needs no cleanup) or when the seat withdraws the verdict.
  2. SKILL.md decision-box rule: a needs-user-decision card carries the same 速读 shape above its four-facet analysis, so the maintainer reads the options in business terms first.
  3. scripts/pm/ensure-pm-labels.sh: the needs-user-decision description gains its PR meaning ("on a PR: awaiting the maintainer's review; a 维护者速读 comment carries the brief") — within the 100-character cap.
  4. The language rule: the 速读 is the third Chinese exception on GitHub (with round reports and verbatim maintainer quotes), stated where the language rule lives.
    Line-neutral on SKILL.md (811/811, headroom 0 — fold, never raise); the patrol row for the half-state (a governed PR with ACCEPT and no label, or a label with no 速读) is a separate card blocked behind check-half-states: read the landed release rule — H1/H24 prose says the definitional readings, and a new report-only row catches a Release: newer than the last Claim: with the assignee still set (and the exit that left no record) #15884, which holds check-half-states.mjs.

Serial

SKILL.md and ensure-pm-labels.sh are in no flight (PR #15848 and #15795 landed). Governed ⇒ draft PR, in-seat review at contract tier, os-zhuang + hotlong, human merge — and, per this very rule, needs-user-decision + a 速读 on it.

Dedup

REST enumeration 2026-09-05T13:20Z, state=all sorted by update (1,200 items, 800 issues; positive control #15846 hit): no card proposes a maintainer-facing brief or a list-view label on governed PRs; the needs-user-decision hits are the label's existing card meaning.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions