Skip to content
Back to skills

Github Code Review

ASecurity

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

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 14, 2026
ai-agentsgotestingcode-reviewgitsecurityperformance

Works with

  • claude code
  • cli

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 14, 2026

npx -y skills add ctaxnagomi/agent-kd-skill --skill github-code-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Code Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Github Code Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ctaxnagomi-github-code-review/badge)](https://www.skillsdirectory.com/skills/ctaxnagomi-github-code-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-code-review
description: "Review PRs: diffs, inline comments via gh or REST."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [github, code-review, pull-requests, git, quality]
---

# GitHub Code Review

Perform code reviews on local changes before pushing, or review open PRs on GitHub. Covers both local git diff review and formal PR reviews with inline comments.

## When to Use

- Before pushing changes (local review)
- Reviewing someone else's PR
- Need to approve or request changes on a PR
- Pre-commit quality check

## Procedure

### Local Review (Pre-Push)

1. Run `git diff` to see unstaged changes
2. Run `git diff --cached` for staged changes
3. Review each change for correctness, style, and safety
4. Check for secrets, credentials, or sensitive data

### PR Review on GitHub

1. List open PRs: `gh pr list`
2. Check out PR locally: `gh pr checkout <number>`
3. Review the diff
4. Leave inline comments on specific lines
5. Submit review: `gh pr review <number> --approve` or `--request-changes`

### Review Checklist

- Correctness: Does the code do what it claims?
- Security: No hardcoded secrets, no injection risks
- Tests: Are new behaviors tested?
- Readability: Clear naming, minimal complexity
- Performance: No obvious bottlenecks

## Pitfalls

- Reviewing too many PRs at once
- Being pedantic about style when linters exist
- Not testing the changes locally
- Approving without actually reading the code

## Verification

- All review comments addressed
- CI passes after changes
- You can explain what each changed file does

---

## How to use?

### 1. Download
Go to the [AGENT KD SKILL gallery](https://ctaxnagomi.github.io/agent-kd-skill/) and find this skill card. Click **Download** to save the SKILL.md file.

### 2. Install
Copy the downloaded SKILL.md into your agent's skills directory:

| Agent | Path |
|-------|------|
| **Hermes** | ~/.hermes/skills/hermes/github-code-review/SKILL.md |
| **opencode** | ~/.config/opencode/skills/github-code-review/SKILL.md |
| **Claude Code** | ~/.claude/skills/github-code-review/SKILL.md |

### 3. Use
Restart your agent session. The skill will auto-load when code review is needed.

### 4. Verify
Ask your agent to review code. If it follows the checklist and provides constructive feedback, you're all set.

Files in this skill

  • SKILL.md2.3 KB
  • assembly.json253 B
  • skill.json618 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.