om-review-prs - SKILL.md Agent Skill

name: om-review-prs description: Review all currently unreviewed open pull requests, newest first, using the auto-review-pr skill and respecting in-progress locks.

Review PRs

Use this as a day-start review queue. It finds unreviewed open PRs, shows the queue, then runs the full om-auto-review-pr workflow one PR at a time.

Workflow

1. Fetch open PRs

gh pr list --state open --json number,title,url,author,labels,reviewDecision,createdAt,updatedAt,isDraft,assignees --limit 50
CURRENT_USER=$(gh api user --jq '.login')

2. Filter to PRs that still need review

Keep PRs where all of the following are true:

not draft
reviewDecision is empty or REVIEW_REQUIRED
author is not $CURRENT_USER
does not carry do-not-merge or blocked
does not carry in-progress
has no assignee other than $CURRENT_USER

3. Sort newest first

Most recently created PRs should be reviewed first.

4. Present the queue

## Review Queue — {date}

Found {count} unreviewed PRs (newest first):

| # | Title | Author | Created | Labels |
|---|-------|--------|---------|--------|
| [#456](url) | Add catalog search | @bob | 2h ago | `feature`, `review` |

5. Review sequentially

For each PR:

Print Reviewing PR #{number}: {title} ({index} of {total})
Run the full .ai/skills/om-auto-review-pr/SKILL.md workflow
Record the verdict
Continue to the next PR

Between PRs, report progress briefly:

Reviewed {done}/{total}. Next: #{number}

6. Final summary

## Review Session Complete

| # | Title | Verdict | Label |
|---|-------|---------|-------|
| #456 | Add catalog search | APPROVED | merge-queue |
| #445 | Fix auth redirect | CHANGES REQUESTED | changes-requested |

If the queue is empty, say so and suggest running om-merge-buddy instead.

Rules

Never silently skip an eligible PR.
If a PR cannot be reviewed right now, include the reason in the session summary and move on.
Respect existing in-progress locks; never auto-force in batch mode.
Reuse the full om-auto-review-pr skill rather than inventing a lighter review path.
Optionally suggest om-merge-buddy after the session so the user can see what is now merge-ready.