pr-review
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR.
How do I install this agent skill?
npx skills add https://github.com/significant-gravitas/autogpt --skill pr-reviewIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates GitHub Pull Request reviews by fetching PR metadata, descriptions, and diffs using the GitHub CLI. It analyzes the code for security and quality issues and posts feedback directly to the PR. While it processes untrusted PR content, this is inherent to its primary function.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerwarn
1/1 file flagged
What does this agent skill do?
PR Review
Find the PR
gh pr list --head $(git branch --show-current) --repo Significant-Gravitas/AutoGPT
gh pr view {N}
Read the PR description
Before reading code, understand the why, what, and how from the PR description:
gh pr view {N} --json body --jq '.body'
Every PR should have a Why / What / How structure. If any of these are missing, note it as feedback.
Read the diff
gh pr diff {N}
Fetch existing review comments
Before posting anything, fetch existing inline comments to avoid duplicates:
gh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/comments --paginate
gh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/reviews
What to check
Description quality: Does the PR description cover Why (motivation/problem), What (summary of changes), and How (approach/implementation details)? If any are missing, request them — you can't judge the approach without understanding the problem and intent.
Correctness: logic errors, off-by-one, missing edge cases, race conditions (TOCTOU in file access, credit charging), error handling gaps, async correctness (missing await, unclosed resources).
Security: input validation at boundaries, no injection (command, XSS, SQL), secrets not logged, file paths sanitized (os.path.basename() in error messages).
Code quality: apply rules from backend/frontend CLAUDE.md files and root AGENTS.md, including its "User-facing copy" section (text a person reads says workflow, never agent or graph).
Design system (frontend): hold changed code under autogpt_platform/frontend/src/**/*.{tsx,ts,css} to the rules in docs/engineering/design-system.md. pnpm lint fails new violations (raw palette classes, hex colours, dark: classes, legacy imports, restyled primitives, reason-less suppressions) and any file whose count goes over its entry in scripts/eslint-rules/design-system-baseline.json; grandfathered counts at or below the baseline pass. Review what lint cannot see: a raised baseline count for a file that was not moved, renamed or split, a colour swapped to a role with a different value (pixels change), global CSS for DOM we render as JSX, a repeated class string that should be a variant, and missing before/after screenshots for changes to src/components/**, globals.css or tailwind*.ts.
Architecture: DRY, single responsibility, modular functions. Security() vs Depends() for FastAPI auth. data: for SSE events, : comment for heartbeats. transaction=True for Redis pipelines.
Testing: edge cases covered, colocated *_test.py (backend) / __tests__/ (frontend), mocks target where symbol is used not defined, AsyncMock for async.
Output format
Every comment must be prefixed with 🤖 and a criticality badge:
| Tier | Badge | Meaning |
|---|---|---|
| Blocker | 🔴 **Blocker** | Must fix before merge |
| Should Fix | 🟠 **Should Fix** | Important improvement |
| Nice to Have | 🟡 **Nice to Have** | Minor suggestion |
| Nit | 🔵 **Nit** | Style / wording |
Example: 🤖 🔴 **Blocker**: Missing error handling for X — suggest wrapping in try/except.
Post inline comments
For each finding, post an inline comment on the PR (do not just write a local report):
# Get the latest commit SHA for the PR
COMMIT_SHA=$(gh api repos/Significant-Gravitas/AutoGPT/pulls/{N} --jq '.head.sha')
# Post an inline comment on a specific file/line
gh api repos/Significant-Gravitas/AutoGPT/pulls/{N}/comments \
-f body="🤖 🔴 **Blocker**: <description>" \
-f commit_id="$COMMIT_SHA" \
-f path="<file path>" \
-F line=<line number>
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/significant-gravitas/autogpt/pr-review">View pr-review on skillZs</a>