fvadicamo/dev-agent-skills / plugins/github-workflow/skills/github-pr-review
github-pr-review
VerifiedHandles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or triage PR comments. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.2 KB |
| references/coderabbit_parsing.md | markdown | 8.8 KB |
| references/severity_guide.md | markdown | 6.7 KB |
references/severity_guide.md
View on GitHub# Severity guide
Reference guide for interpreting severity levels from automated review comments (Gemini, CodeRabbit, Cursor, and others).
## Severity Badges
Gemini uses visual badges in review comments to indicate severity:
### CRITICAL
**Badge**: ``
**Visual**: Red badge with "critical" text
**Meaning**: Must be fixed before merge. Indicates:
- Security vulnerabilities
- Data loss risks
- Logic errors causing incorrect behavior
- Infinite loops or deadlocks
- Memory leaks or resource exhaustion
**Action**: Stop and fix immediately. These block merge.
---
### HIGH
**Badge**: ``
**Visual**: Orange badge
**Meaning**: Should be fixed. Indicates:
- Performance issues
- Error handling gaps
- Potential race conditions
- Missing validation on important paths
**Action**: Address before merge unless there's a strong reason not to.
---
### MEDIUM
**Badge**: ``
**Visual**: Yellow badge
**Meaning**: Recommended fix. Indicates:
- Code style issues
- Minor refactoring opportunities
- Unreachable code (dead code)
- Duplicate logic
- Missing edge case handling
**Action**: Address if time permits, or create follow-up issue.
---
### LOW
**Badge**: ``
**Visual**: Blue/gray badge
**Meaning**: Optional improvement. Indicates:
- Import ordering
- Naming conventions
- Documentation suggestions
- Minor style preferences
**Action**: Optional. Can be skipped with justification.
---
## Detection Patterns
### Gemini Badge Detection (Primary for Gemini)
```python
# In comment body, look for:
"critical.svg" → CRITICAL
"high-priority.svg" → HIGH
"medium-priority.svg" → MEDIUM
"low-priority.svg" → LOW
```
### CodeRabbit Detection
CodeRabbit does **not** use SVG badges. It uses emoji + italic text in the comment body.
The pattern is: `_<emoji> <label>_` or `_<emoji> <label>_ | _<color> <severity>_`
CodeRabbit classifies comments along two axes: **type** (what kind of issue) and **severity** (how impactful).
#### Comment types (primary label)
| Comment pattern | Severity |
|----------------|----------|
| `_🔒 Security_` or `_🚨 Critical_` | CRITICAL |
| `_⚠️ Potential issue_` | HIGH |
| `_🐛 Bug_` | HIGH |
| `_⚡ Performance_` | HIGH |
| `_🛠️ Refactor suggestion_` | MEDIUM |
| `_💡 Suggestion_` | MEDIUM |
| `_🧹 Nitpick_` | LOW (only in assertive mode) |
| `_🔧 Optional_` | LOW (skip by default) |
#### Severity levels (secondary color badge)
When a secondary color badge is present, use it as the **binding** severity indicator
(it overrides the type-based default above):
| Secondary badge | Official name | Maps to |
|----------------|---------------|---------|
| `_🔴 Critical_` | Critical | CRITICAL |
| `_🟠 Major_` | Major | HIGH |
| `_🟡 Minor_` | Minor | LOW |
| `_🔵 Trivial_` | Trivial | LOW (skip by default) |
| `_⚪ Info_` | Info | LOW (informational, no action needed) |
Note: some older reviews may use `_🔵 Info_` instead of `_🔵 Trivial_`. Treat both as LOW.
#### Assertive vs chill mode
CodeRabbit has two profiles configured via `.coderabbit.yaml`:
- `profile: chill` (default) - lighter feedback, nitpicks are hidden
- `profile: assertive` - full feedback, includes nitpick comments
When reviewing a repo in `chill` mode, nitpick sections will not appear in the review body.
**CodeRabbit non-inline comments** (outside diff, duplicate, nitpick) are not posted
as inline review comments. They are embedded in the PR-level review body
(`pulls/$PR/reviews`) inside structured `<details>` blocks. Each section type
has its own block with file paths, line ranges, severity, and optional AI prompts.
See `coderabbit_parsing.md` for the full body structure and parsing guide.
**Duplicate comments** from CodeRabbit indicate an issue was already flagged in a
previous review and not fixed. Treat these as higher actual priority than their
severity label suggests.
### Cursor Comments
```
<!-- **High Severity** --> → HIGH
<!-- **Medium Severity** --> → MEDIUM
```
### Keyword Detection (Fallback)
When badges or HTML comments aren't present, infer from keywords:
| Keywords | Severity |
|----------|----------|
| security, vulnerability, injection, XSS, SQL | CRITICAL/HIGH |
| dangerous, unsafe, exploit | CRITICAL |
| performance, slow, O(n²) | HIGH |
| error handling, exception, catch | HIGH |
| unreachable, dead code, unused | MEDIUM |
| refactor, simplify, consolidate | MEDIUM |
| style, formatting, PEP, naming | LOW |
| import order, whitespace | LOW |
---
## Related Comments Detection
Comments are often related when:
1. **Consequence relationship**: Comment B is a consequence of fixing Comment A
- Keywords: "consequence", "result of", "as mentioned above"
2. **Same root cause**: Multiple comments about the same underlying issue
- Keywords: "root cause", "same issue", "related to"
3. **Unreachable code**: After an exception handling fix, related `except` blocks may become unreachable
- Pattern: CRITICAL exception handling → MEDIUM unreachable code
4. **Same function/method**: Comments within ~100 lines in the same file, where one is CRITICAL and others are MEDIUM/LOW
---
## Example: Exception Handling Pattern
Common scenario from Gemini reviews:
**Comment 1 (CRITICAL)**: Exception handling in `method_x()` needs refactoring:
- FileNotFoundError should fail-fast, not retry
- Generic exceptions need sleep to avoid busy-loop
**Comment 2 (MEDIUM)**: `except FileNotFoundError` block at line 186 is unreachable
→ This is a CONSEQUENCE of fixing Comment 1
**Comment 3 (MEDIUM)**: `except FileNotFoundError` block at line 473 is unreachable
→ Also a CONSEQUENCE of fixing Comment 1
**Resolution**: Fix Comment 1 first. Comments 2 and 3 will be automatically resolved.
---
## Gemini Config Reference
Gemini behavior is controlled by `.gemini/config.yaml`:
```yaml
code_review:
threshold: LOW # Minimum severity to report
auto_fix: false # Whether to suggest auto-fixes
blocking: false # Whether reviews block merge
```
When `threshold: LOW`, all severities are reported.
When `blocking: false`, reviews are advisory only.
---
## Workflow Integration
1. **Fetch comments**: Parse severity from badge URLs in comment body
2. **Sort by severity**: CRITICAL → HIGH → MEDIUM → LOW
3. **Group related**: Use heuristics above
4. **Process CRITICAL first**: These often resolve MEDIUM/LOW comments
5. **Skip LOW if needed**: They're optional by definition
---
## References
- [Gemini Code Assist Documentation](https://cloud.google.com/gemini/docs/discover/code-assist)
- [GitHub PR Review API](https://docs.github.com/en/rest/pulls/comments)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse 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 | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |