Skip to content

aboylabs/ai-agent-skills / skills/github/github-code-review

github-code-review

Flagged

Review PRs: diffs, inline comments via gh or REST.

FileKindSize
SKILL.mdskill md13.4 KB
references/review-output-template.mdmarkdown2.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.
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall