메뉴
Detect pull requests aging past warn / critical thresholds, score severity, and nudge reviewers via Slack DM, channel, email, or directly as a PR comment — with one-time auto-escalation when a PR hits critical so velocity stops leaking through review queues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Correlate near-in-time events across PR merges, deploys, monitoring (Sentry/NewRelic/Datadog/AppDynamics) and ticket trackers (Jira/Azure DevOps) into confidence-scored clusters that answer "which deploy caused this bug" without manual tab-switching.
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
A paranoid OWASP-Top-10-aware system prompt for AI code review that traces data flow, treats every input as malicious, maps each finding to an OWASP category, and outputs a structured Summary / Findings / Severity / Score block reviewers can act on.
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
| name | review-backlog-killer |
| description | Detect pull requests aging past warn / critical thresholds, score severity, and nudge reviewers via Slack DM, channel, email, or directly as a PR comment — with one-time auto-escalation when a PR hits critical so velocity stops leaking through review queues. |
| tags | ["code-review","pull-request","slack","devex","ai-agent"] |
| publisher | agena |
Pull requests get lost in review queues; team velocity drops silently. Sprint planning shows it as "I dunno, sometimes the reviewers are slow". This pattern surfaces stuck PRs deterministically and sends the reviewer a nudge through whichever channel they actually read.
Define open: PR is open when merged_at IS NULL AND closed_at IS NULL AND its provider status is in {open, opened, pending, review_required, in_review, active}. PRs with provider status in
{abandoned, declined, closed, rejected} drop off the backlog.
Configure thresholds per workspace (chip-pick is best UX — 6h / 12h / 1d / 2d / 3d / 1w / custom). Defaults: 24h warn, 48h critical, 6h between auto-nudges to the same reviewer.
Poller every 30 minutes updates age_hours and severity
(info < warn ≤ warning < critical ≤ critical) on every open PR.
Merged or closed PRs auto-resolve out of the backlog.
Pick a notify channel per workspace:
slack_dm — direct, most attentionslack_channel — visible to teamemail — for async-first teamspr_comment — most attention-grabbing because it lands where
the reviewer already lives. The comment text is locale-aware so
non-English teams don't get an English nudge.manual — dashboard-only, no auto-notifyAuto-escalate once when a PR crosses the critical threshold:
set escalated_at, mark severity, surface above the fold to tech
leads. Fire it once per PR, not on every poll cycle.
Manual nudge button on every row — fires the configured channel immediately, overrides the interval. Useful for a tech lead doing a one-shot push before standup.
⏱️ AGENA Review Backlog
This PR has been waiting for review for **47 hours** (severity: critical).
Nudge #2.
Configure thresholds at /dashboard/review-backlog.
When the Reviews module is also on, the message includes
AGENA review score: 84 so reviewers see the time investment before
clicking.