aboylabs/ai-agent-skills / skills/github/github-code-review
github-code-review
FlaggedReview PRs: diffs, inline comments via gh or REST.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.4 KB |
| references/review-output-template.md | markdown | 2.4 KB |
references/review-output-template.md
View on GitHub# Review Output Template
Use this as the structure for PR review summary comments. Copy and fill in the sections.
## For PR Summary Comment
```markdown
## Code Review Summary
**Verdict: [Approved β
| Changes Requested π΄ | Reviewed π¬]** ([N] issues, [N] suggestions)
**PR:** #[number] β [title]
**Author:** @[username]
**Files changed:** [N] (+[additions] -[deletions])
### π΄ Critical
<!-- Issues that MUST be fixed before merge -->
- **file.py:line** β [description]. Suggestion: [fix].
### β οΈ Warnings
<!-- Issues that SHOULD be fixed, but not strictly blocking -->
- **file.py:line** β [description].
### π‘ Suggestions
<!-- Non-blocking improvements, style preferences, future considerations -->
- **file.py:line** β [description].
### β
Looks Good
<!-- Call out things done well β positive reinforcement -->
- [aspect that was done well]
---
*Reviewed by Hermes Agent*
```
## Severity Guide
| Level | Icon | When to use | Blocks merge? |
|-------|------|-------------|---------------|
| Critical | π΄ | Security vulnerabilities, data loss risk, crashes, broken core functionality | Yes |
| Warning | β οΈ | Bugs in non-critical paths, missing error handling, missing tests for new code | Usually yes |
| Suggestion | π‘ | Style improvements, refactoring ideas, performance hints, documentation gaps | No |
| Looks Good | β
| Clean patterns, good test coverage, clear naming, smart design decisions | N/A |
## Verdict Decision
- **Approved β
** β Zero critical/warning items. Only suggestions or all clear.
- **Changes Requested π΄** β Any critical or warning item exists.
- **Reviewed π¬** β Observations only (draft PRs, uncertain findings, informational).
## For Inline Comments
Prefix inline comments with the severity icon so they're scannable:
```
π΄ **Critical:** User input passed directly to SQL query β use parameterized queries to prevent injection.
```
```
β οΈ **Warning:** This error is silently swallowed. At minimum, log it.
```
```
π‘ **Suggestion:** This could be simplified with a dict comprehension:
`{k: v for k, v in items if v is not None}`
```
```
β
**Nice:** Good use of context manager here β ensures cleanup on exceptions.
```
## For Local (Pre-Push) Review
When reviewing locally before push, use the same structure but present it as a message to the user instead of a PR comment. Skip the PR metadata header and just start with the severity sections.
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 |