메뉴
Maintainer triage on OTHER people's PRs/MRs — verdict of approve, supersede, or close, salvage with credit, close the cluster. Use for a review batch, a pasted Discord thread with a PR, or salvage/supersede/close asks. Not for your own PR (that's pr-ready).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff pass, not a test run and not a subagent sweep. Use for /clean, "clean it up", "tidy this", and automatically before creating, updating, or automerging a PR or moving to the next one.
The general profile-driven perf loop for any language or runtime: baseline, profile, fix the real hot path, re-measure. Use for /perf, "this is slow", or optimization work.
Prove a visual change by looking at the rendered surface — screenshot it and compare to the reference before saying done. Use after any UI, layout, theme, or color change, or when the user says it still looks wrong or doesn't match.
Clear everything blocking an existing PR/MR from merging — rebase onto the default branch, get CI green, and resolve review threads (Copilot and human). Use for "rebase on main", "make CI green", "fix CI/CD", "address the reviews", "address Copilot", "review-loop", or "get this mergeable".
Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff. Preserves any media already in the body. Use when the user says /pr-update, open a PR, update the PR, refresh the PR title/description, or wants the PR opener/manager flow.
Look it up before answering or building — this project's documents of record first, then external prior art. Use when the user says research, look it up, sleuth GitHub, "what do other people do", "is that a thing", "are you sure", or asks for something that has obviously been solved before.
| name | pr-triage |
| description | Maintainer triage on OTHER people's PRs/MRs — verdict of approve, supersede, or close, salvage with credit, close the cluster. Use for a review batch, a pasted Discord thread with a PR, or salvage/supersede/close asks. Not for your own PR (that's pr-ready). |
Maintainer triage. Three real outcomes: approve, supersede (salvage +
credit + close the old one), or close (wrong premise). Verdict first; wait
for an explicit go before forge writes (approve / supersede / close / merge /
push). Use gh or glab.
Batch ("we will be reviewing…") or a pasted Discord/>>>…<<< thread with a PR:
AGENTS.md / CONTRIBUTING.md if present.More than one PR/issue in front of you? Group them by the fix they need before you judge any single one. Multiple PRs on the same bug (or fragile subsystem) are one consolidation, not N salvages.
Co-authored-by + @handle), and supersede the whole cluster.#68665 + #63590 + #67603 → one super-PR,
then run the per-PR loop within each group to confirm premises.Do not enumerate one verdict per PR when they share a fix — that's the lazy shape. One cluster → one consolidated supersede.
A pasted thread is the intake. Don't make them restate a bare URL.
| Action | GitHub | GitLab |
|---|---|---|
| View | gh pr view <N> | glab mr view <N> |
| Diff | gh pr diff <N> | glab mr diff <N> |
| Comment | gh pr comment <N> | glab mr note <N> |
| Review | gh pr review <N> --approve | --request-changes | glab mr approve / note |
| Close PR/MR | gh pr close <N> | glab mr close <N> |
| Close issue | gh issue close <N> | glab issue close <N> |
git fetch origin pull/<N>/head:refs/remotes/origin/pr-<N> # GitHub
# GitLab: glab mr checkout <N>
Run this within each cluster (see "Cluster the batch first"). If the group consolidates, the salvage plan is shared and you supersede all of them into one super-PR — don't emit a standalone salvage per member.
gh / glab).main).**PR/MR:** [#N](https://…/pull/N)
**Verdict: approve | supersede | close-as-wrong-premise**
**Worktree:** `…` · `<branch>`
### Why
- …
### Checks
| Check | Result |
|---|---|
| Merges onto default branch | … |
| CI | … |
| Targeted tests | … |
### Next (after go)
- approve: …
- supersede: salvage plan (reuse X, drop Y, tests Z, credit @handle)
- close: wrong-premise comment outline
| Situation | Verdict |
|---|---|
| Idea + shape are fine | approve |
| Idea is right, shape is wrong (wrong helper/layer, missing tests for the bug class, contaminated, stale/conflicting, duplicate of another PR, ignored lead feedback) | supersede |
| Premise doesn't hold on current default branch | close-as-wrong-premise |
Anti-patterns — do not do these:
keep open — ask the author to rewrite / reuse helper X / add coverage
when the shape is already wrong → that is supersede. You salvage it.request-changes, needs-info, wait-and-see)
for external PRs that need reshaping.request-changes is not a triage verdict. It is only for trusted /
internal authors with a single tiny nit under Approve — never for
"please rebuild this correctly."
Infer from organization membership, team roles, prior maintainer behavior, or the user explicitly identifying someone as a lead/internal contributor.
| Who | Default |
|---|---|
| #1 lead | Prefer approve/merge. Don't supersede automatically. Never approve over their open review comments. |
| Other internal | Prefer approve. One tiny nit → ask them (request-changes). Needs a real rewrite → supersede (or they bounce it to you). |
| External | Normal bar. Idea right / shape wrong → supersede with credit. Never "ask them to rebuild it." |
Not enough alone: taste nits, optional follow-ups, "could be prettier."
This is the default salvage ritual — not a rare escalation.
Co-authored-by +
@handle for each in the body.Supersedes #N, #M, … for all members;
Closes/Fixes only for issues it really fixes.no-tropes on public comments.Templates: reference.md.
After supersede or a merge that kills siblings:
Superseded by #<new>., then close.Closes # on the new PR, or close by hand).Run this checklist at the end of each PR/item — don't wait to be reminded:
Closes # on the new PR).pr-update) and CI is green.