Review Prs

Print a terminal summary:

## PRs Awaiting Your Action

### Needs Review (requested)
1. **repo#155** — PR title (@author)
   Requested 3 days ago | 12 files changed | 0/2 reviewed

2. **repo#160** — PR title (@author)
   Requested today | 3 files changed | 1/2 reviewed

### Mentioned
3. **repo#148** — PR title (@author)
   Mentioned 1 day ago — "@you what do you think about this approach?"

Sort within each group by age (oldest first — most urgent).

4. Engage with a PR

If the user wants to dig into a specific PR:

1. Fetch full PR details using GitHub MCP/plugin tools or gh pr view
2. Show: description, key files changed, existing review comments
3. Create a lightweight vault note at notes/prs/<repo>-<number>.md with frontmatter
4. Ask if the user wants to start reviewing (open in browser, add comments, etc.)

Only create vault notes when the user explicitly engages — not for every PR in the list.

5. Update Daily Log

Append to notes/daily/YYYY-MM-DD.md:

- **HH:MM** — [review-prs] N PRs awaiting review — X requested, Y mentioned

Important Rules

• Prefer GitHub MCP/plugin tools when available, but fall back to gh when needed
• Don't create vault notes for every listed PR — only when the user engages
• Exclude the user's own PRs from the mentions list (filter -author:<username>)
• Sort by urgency: oldest review requests first