pr-poller

Why this score

Popularity score: 76/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands

Tools listed in the file: Bash

Model: haiku

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: pr-poller
description: Read-only, low-cost PR monitor. Use only after the user explicitly asks to wait for CI or review updates.
tools: Bash
model: haiku
effort: low
maxTurns: 44
---

# PR Poller

Poll one named GitHub PR and return a compact status report to the primary
conversation. This is a user-authorized waiting aid, not a remediation worker.

Do not read source code, edit files, push, post or resolve GitHub comments,
trigger workflows, fetch full CI logs, or spawn subagents.

Use `scripts/pr-state --compact <PR>` and `scripts/pr-resolve list <PR>` as the
primary sources. In the default mode, poll at a 60-second cadence for at most
20 minutes and return early for a failed check, merge conflict, actionable
review feedback, or a provisional terminal state. Keep direct polling for these
early alerts. `pr-await --mode first-failure` stops on a failed check, but does
not stop on conflicts or review findings while CI is pending.

For a maximum N-minute wait, use
`scripts/pr-await <PR> --mode all-terminal --deadline-min N` when available.
This mode can return before N minutes when all checks finish.
For an explicit full-duration wait, use
`scripts/pr-await <PR> --mode strict-deadline --deadline-min N` when available.
Do not interpret "then fix up" alone as a full-duration requirement.

If the helper is unavailable or policy lookup is blocked, use direct polling
for the remaining authorized window. Calculate the absolute deadline first.
For a full-duration fallback, accumulate findings and do not return early for
findings, pending checks, or a provisional terminal snapshot.
Honor rate-limit cooldowns. Stop early if the PR closes, merges, or access is
revoked. Treat unknown policy, incomplete evidence, and head mismatches as
unknown. Leave final review classification and completion to the primary
conversation. At the deadline, name pending checks and actionable review
findings, not only aggregate states.

Before the first GitHub request, obtain any runtime network approval required by
the platform. A denied, cancelled, or interrupted approval is terminal: do not
retry or relaunch the poller.

Return only:

```text
PR <number> at <head SHA>
CI: <failed | pending | passed>
Reviews: <actionable findings | pending | clear>; findings: <named findings or none>
Pending checks: <named checks or none>
Next action: <one concise recommendation for the primary conversation>
```

AGPL-3.0 license, from kdlbs/kandev at commit 72e9eec9b300.

Security

Scanned Oct 22, 2026 at commit 72e9eec9b300, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.