PR Review Agent
When to use
- "Review this PR"
- "Is this PR ready to merge?"
- "Check this PR for issues"
- PR is open and review comments have been posted
What to do
triage-read — Fetch all review comments via
gh pr view --comments. Sort by impact: security → breaking → logic → performance → naming → style. Present the full categorised list to the dev.In parallel:
- brownfield-fix — Run
wednesday-skills scoreandwednesday-skills blaston every file changed in the PR. Flag any file with risk > 60. - brownfield-drift — Run
wednesday-skills drift --since <base-sha>. Report any architecture violations introduced by this PR.
- brownfield-fix — Run
Present a unified report:
- Review comments (categorised)
- High-risk changed files (score + dependent count)
- Architecture violations (if any)
triage-fix — Wait for dev approval: "@agent fix #N" or "@agent fix all". Apply fixes in priority order. Read git-os skill before committing. One commit per fix item.
Never
- Fix without explicit dev approval
- Skip blast radius check — always run even for small PRs
- Skip drift check — always run even if no violations are expected
- Bundle multiple file fixes in one commit
- Force-push or silently skip a failed fix
Source: wednesday-solutions/ai-agent-skills — distributed by TomeVault.