Pr review agent
Skill wednesday-solutions/ai-agent-skills/skills/agents/pr-review-agent
Pre-configured agent skills for Vibe Coded projects. These skills provide AI coding assistants (Claude Code, Cursor, etc.) with specific guidelines for code quality and design standards.
npx -y skills add wednesday-solutions/ai-agent-skills --skill pr-review-agentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Full PR review orchestrator. Use when asked to review a PR or check if it is ready to merge. Runs blast radius + drift check on changed files, then hands off to pr-review for comment triage and fixes. Do NOT use pr-review directly for full reviews — use this.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.9 KB, as published. Nobody here has run it
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