pr-review

Name: pr-review
Author: wednesday-solutions

161stars19forks

How to install pr-review?

wednesday-solutions/ai-agent-skills/pr-review

$npx -y skills add wednesday-solutions/ai-agent-skills --skill pr-review

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# PR Review — Gemini Fix Queue
2
3	## Trigger
4
5	Load this skill when a dev wants to act on PR review comments:
6	- "Fix the review comments"
7	- "Triage the PR feedback"
8	- "Apply fixes from the review"
9	- "@agent fix #1 #3"
10	- "@agent fix all"
11	- "What do I need to fix in this PR?"
12
13	Also triggered automatically by GitHub Actions when Gemini bot posts a PR review.
14
15	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.
16
17	## Priority Order
18
19	Fix in this order — lower number = fix first.
20
21	\| Rank \| Category \| Examples \|
22	\|------\|----------\|---------\|
23	\| 1 \| security \| auth issues, injection risks, data exposure \|
24	\| 2 \| breaking \| API contract changes, interface changes \|
25	\| 3 \| logic \| wrong conditions, missing edge cases \|
26	\| 4 \| performance \| N+1 queries, unnecessary re-renders \|
27	\| 5 \| naming \| variable/function/class names, casing \|
28	\| 6 \| style \| formatting, whitespace, import order \|
29
30	Rule: never fix a style item while a security or breaking issue is pending.
31
32	## Review Report Format
33
34	```markdown
35	# Gemini Review — PR #<n>
36
37	\| # \| Category \| File \| Issue \| Status \|
38	\|---\|----------\|------\|-------\|--------\|
39	\| 1 \| security \| src/db.js \| SQL query not parameterized \| ⬜ pending \|
40	\| 2 \| logic \| src/user.js \| Missing null check on user.profile \| ⬜ pending \|
41	\| 3 \| naming \| src/auth.js \| Variable `x` is unclear \| ⬜ pending \|
42
43	To fix: `@agent fix #1 #2` Fix all: `@agent fix all`
44	```
45
46	## Tools
47
48	\| Action \| Tool \|
49	\|--------\|------\|
50	\| Read a file before applying a fix \| `Read` \|
51	\| Apply a fix to a file \| `Edit` \|
52	\| Run git commands (commit, push) \| `Bash` \|
53	\| Search for a pattern across files \| `Grep` \|
54	\| Find files by name \| `Glob` \|
55
56	## Agent Fix Rules
57
58	- Never auto-fix without explicit dev approval (`@agent fix #N`)
59	- Read `git-os` SKILL.md before making any commit
60	- One commit per fix item
61	- Commit format: `fix(scope): description\n\nResolves review item #N`
62	- Push to the same PR branch
63	- Update the report — mark fixed items as `✅ fixed`
64
65	## Failure Handling
66
67	If a fix cannot be applied cleanly, post a comment explaining the conflict. Never force-push or silently skip a fix.

People who liked this also viewed

6 picks

Type

pr-review

161stars19forks

View on GitHub

How to install pr-review?

wednesday-solutions/ai-agent-skills/pr-review

$npx -y skills add wednesday-solutions/ai-agent-skills --skill pr-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PR Review — Gemini Fix Queue
2
3	## Trigger
4
5	Load this skill when a dev wants to act on PR review comments:
6	- "Fix the review comments"
7	- "Triage the PR feedback"
8	- "Apply fixes from the review"
9	- "@agent fix #1 #3"
10	- "@agent fix all"
11	- "What do I need to fix in this PR?"
12
13	Also triggered automatically by GitHub Actions when Gemini bot posts a PR review.
14
15	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.
16
17	## Priority Order
18
19	Fix in this order — lower number = fix first.
20
21	\| Rank \| Category \| Examples \|
22	\|------\|----------\|---------\|
23	\| 1 \| security \| auth issues, injection risks, data exposure \|
24	\| 2 \| breaking \| API contract changes, interface changes \|
25	\| 3 \| logic \| wrong conditions, missing edge cases \|
26	\| 4 \| performance \| N+1 queries, unnecessary re-renders \|
27	\| 5 \| naming \| variable/function/class names, casing \|
28	\| 6 \| style \| formatting, whitespace, import order \|
29
30	Rule: never fix a style item while a security or breaking issue is pending.
31
32	## Review Report Format
33
34	```markdown
35	# Gemini Review — PR #<n>
36
37	\| # \| Category \| File \| Issue \| Status \|
38	\|---\|----------\|------\|-------\|--------\|
39	\| 1 \| security \| src/db.js \| SQL query not parameterized \| ⬜ pending \|
40	\| 2 \| logic \| src/user.js \| Missing null check on user.profile \| ⬜ pending \|
41	\| 3 \| naming \| src/auth.js \| Variable `x` is unclear \| ⬜ pending \|
42
43	To fix: `@agent fix #1 #2` Fix all: `@agent fix all`
44	```
45
46	## Tools
47
48	\| Action \| Tool \|
49	\|--------\|------\|
50	\| Read a file before applying a fix \| `Read` \|
51	\| Apply a fix to a file \| `Edit` \|
52	\| Run git commands (commit, push) \| `Bash` \|
53	\| Search for a pattern across files \| `Grep` \|
54	\| Find files by name \| `Glob` \|
55
56	## Agent Fix Rules
57
58	- Never auto-fix without explicit dev approval (`@agent fix #N`)
59	- Read `git-os` SKILL.md before making any commit
60	- One commit per fix item
61	- Commit format: `fix(scope): description\n\nResolves review item #N`
62	- Push to the same PR branch
63	- Update the report — mark fixed items as `✅ fixed`
64
65	## Failure Handling
66
67	If a fix cannot be applied cleanly, post a comment explaining the conflict. Never force-push or silently skip a fix.

People who liked this also viewed

6 picks

Type