pr-review-triage

星标1

分支1

更新时间2026年6月22日 00:37

Use for an Engram PR babysitter triage loop that monitors PR aging, CI blocks, reviewer threads, and lightweight action proposals with isolated-worktree fix candidates and human escalation for risky changes.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

aiconnai

aiconnai/engram

打开 GitHub 仓库查看创作者相关仓库

下载

PR Babysitter Triage Loop

Use this skill for PR queue hygiene on a weekly or 5 to 15 minute cadence. The default mode is proposal-only unless a low-risk L2 fix candidate passes the gate. Pair it with skills/loop-engineering/SKILL.md for global loop controls.

Inputs

Open PR list and labels.
CI status per PR.
Required reviewer threads and blocking comments.
Current pr-babysitter-state.md, history, run log, and budget file.
Current denylist and auto-merge allowlist.

Output

Append a concise triage block:

## High Priority
- PR:
  Blocking condition:
  Why it blocks delivery:
  Exact action:
  Risk level:

## Watch

## Human Escalation

## State Updates
- Attempts already made:
- Last action taken:
- Who or what is next:

Execution Gate

Only propose an isolated-worktree fix when all of these are true:

CI is red or there is a clear review block.
Attempts are below 3.
The issue is a single-file or small-diff candidate.
The path is not denylisted.
A verifier is available after the implementer.

Decision Matrix

Low-risk minimal fix candidate: spawn minimal-fix, then loop-verifier.
Medium or high risk, ambiguity, or path risk: append to triage inbox and escalate to a human.
No actionable PRs: exit report-only after updating state and run log.

Rules

Do not auto-merge without an explicit allowlist.
Do not resolve reviewer comments unless the verifier confirms the diff and intent.
Do not edit auth, storage migrations, protocol surfaces, attestation/snapshot code, production infrastructure, secrets, release workflows, or MCP write tools without human approval.
Prefer a short comment or issue handoff over speculative code changes.

Completion Gate

Mark the run complete only when every high-priority PR has a next action, risk level, owner or escalation path, and run-log entry.

同仓库更多 Skills

同仓库

dependency-triage

aiconnai/engram

Use for an Engram dependency triage loop that watches advisories and lockfiles, proposes patch-only updates, rejects major upgrades without approval, and records reproducible verification commands.

2026-06-221

loop-triage-ci

aiconnai/engram

Use for an Engram CI sweeper triage loop that groups CI failures, classifies root causes, caps attempts, and proposes bounded minimal-fix candidates only after budget, denylist, and verifier gates.

2026-06-221

loop-triage

aiconnai/engram

Use for an Engram daily triage loop that safely collects and classifies CI, issue, PR, commit, and chat signals into report-only handoff state with bounded scope, no auto-fix, and loop-run-log updates.

2026-06-221

loop-engineering

aiconnai/engram

Use when designing, implementing, auditing, hardening, or operating agent loops in this repository, including Claude Code/Grok Build/Codex style `/loop` workflows, explicit `/goal` runs, Git worktree orchestration, MCP and memory automation, sub-agent execution, STATE.md handoffs, cost controls, maker/checker verification, and the Engram security gate (full `sensors.sh` + AgentShield scan + `just ci`). Loops default to L1 report-only; autonomous execution against Engram requires a reviewed ADR per the harness security contract.

2026-06-211

agentshield-scan

aiconnai/engram

Weekly or manual security triage loop that executes AgentShield with a hard iteration cap and records the result in a repository state file.

2026-06-161

engram-council

aiconnai/engram

Run structured consensus with Engram's `memory_council` tool and `CouncilSkill` SDK wrappers for architecture, design, policy, security, reliability, performance, ADR, or tradeoff decisions. Use when the user asks for consensus, council review, multi-agent-style review, decision rationale, option comparison, or mentions `llm-council`, `memory_council`, or `CouncilSkill`. Do not use for simple lookup, single-answer retrieval, or execution-only coding tasks after a decision is already made.

2026-06-041

name	pr-review-triage
description	Use for an Engram PR babysitter triage loop that monitors PR aging, CI blocks, reviewer threads, and lightweight action proposals with isolated-worktree fix candidates and human escalation for risky changes.

PR Babysitter Triage Loop

Inputs

Open PR list and labels.
CI status per PR.
Required reviewer threads and blocking comments.
Current pr-babysitter-state.md, history, run log, and budget file.
Current denylist and auto-merge allowlist.

Output

Append a concise triage block:

## High Priority
- PR:
  Blocking condition:
  Why it blocks delivery:
  Exact action:
  Risk level:

## Watch

## Human Escalation

## State Updates
- Attempts already made:
- Last action taken:
- Who or what is next:

Execution Gate

Only propose an isolated-worktree fix when all of these are true:

CI is red or there is a clear review block.
Attempts are below 3.
The issue is a single-file or small-diff candidate.
The path is not denylisted.
A verifier is available after the implementer.

Decision Matrix

Low-risk minimal fix candidate: spawn minimal-fix, then loop-verifier.
Medium or high risk, ambiguity, or path risk: append to triage inbox and escalate to a human.
No actionable PRs: exit report-only after updating state and run log.

Rules

Do not auto-merge without an explicit allowlist.
Do not resolve reviewer comments unless the verifier confirms the diff and intent.
Do not edit auth, storage migrations, protocol surfaces, attestation/snapshot code, production infrastructure, secrets, release workflows, or MCP write tools without human approval.
Prefer a short comment or issue handoff over speculative code changes.

Completion Gate

Mark the run complete only when every high-priority PR has a next action, risk level, owner or escalation path, and run-log entry.