Pr Review Agent Skill

Fix engine for PR review comments. Fetches review comments (Gemini bot or human), categorizes by impact, posts a prioritized fix queue, and applies fixes on dev approval. Called directly for quick fixes, or internally by pr-review-agent as part of full PR review.

665 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

164

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill pr-review

The instruction itself

7 sections, as written by the author

PR Review — Gemini Fix Queue

Trigger

Load this skill when a dev wants to act on PR review comments:

"Fix the review comments"
"Triage the PR feedback"
"Apply fixes from the review"
"@agent fix #1 #3"
"@agent fix all"
"What do I need to fix in this PR?"

Also triggered automatically by GitHub Actions when Gemini bot posts a PR review.

Do NOT use this skill for: creating a new PR (use pr-create), or committing code (use git-os). This skill only runs on an already-open PR that has review comments on it.

Priority Order

Fix in this order — lower number = fix first.

| Rank | Category | Examples |

|------|----------|---------|

| 1 | security | auth issues, injection risks, data exposure |

| 2 | breaking | API contract changes, interface changes |

| 3 | logic | wrong conditions, missing edge cases |

| 4 | performance | N+1 queries, unnecessary re-renders |

| 5 | naming | variable/function/class names, casing |

| 6 | style | formatting, whitespace, import order |

Rule: never fix a style item while a security or breaking issue is pending.

Review Report Format

# Gemini Review — PR #<n>

| # | Category | File | Issue | Status |
|---|----------|------|-------|--------|
| 1 | security | src/db.js | SQL query not parameterized | ⬜ pending |
| 2 | logic | src/user.js | Missing null check on user.profile | ⬜ pending |
| 3 | naming | src/auth.js | Variable `x` is unclear | ⬜ pending |

To fix: `@agent fix #1 #2`   Fix all: `@agent fix all`

Tools

| Action | Tool |

|--------|------|

| Read a file before applying a fix | Read |

| Apply a fix to a file | Edit |

| Run git commands (commit, push) | Bash |

| Search for a pattern across files | Grep |

| Find files by name | Glob |

Agent Fix Rules

Never auto-fix without explicit dev approval (@agent fix #N)
Read git-os SKILL.md before making any commit
One commit per fix item
Commit format: fix(scope): description\n\nResolves review item #N
Push to the same PR branch
Update the report — mark fixed items as ✅ fixed

Failure Handling

If a fix cannot be applied cleanly, post a comment explaining the conflict. Never force-push or silently skip a fix.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take wednesday-solutions/pr-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.