skills.rest
Heron11
Heron11COMMUNITY
Explore all skills by this author →
GitHub

review

Review code changes for correctness, security, and quality before merging.

Updated Apr 8, 2026
Search Tags:#diff analysis#code review#security#github#agent coordination
One-click install
npx skills add https://github.com/Heron11/otter-code --skill review-heron11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Heron11/otter-code/tree/main/packages/core/src/skills/bundled/review
Command: npx skills add https://github.com/Heron11/otter-code --skill review-heron11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of reviewing code changes by orchestrating git, GH CLI, and multi-agent analysis to flag correctness, security, and quality concerns before code is merged.

Core Features & Use Cases

  • Diff understanding: Detects whether the user wants to review local diffs, a pull request, or specific files and prepares the appropriate git or gh pr context.
  • Specialized agents: Launches four focused reviewers covering correctness/security, code quality, performance, and exploratory auditing, each returning structured findings.
  • Actionable output: Consolidates and verifies results, then optionally posts inline GH comments when the --comment flag is used, ensuring high-confidence recommendations.

Quick Start

Ask /review to inspect the current changes and surface problems across correctness, quality, and performance.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code changes for correctness and security before merging?▼

Code review for correctness and security involves analyzing git diffs and pull requests to flag potential issues before merging. This process inspects local changes or specific files within a GitHub-managed repository to ensure quality standards are met.

Can I automatically post inline comments on a GitHub pull request during code review?▼

Yes, inline GitHub pull request comments can be posted automatically by passing the `--comment` flag. This action consolidates verified code review findings and posts them directly to the pull request thread.

Does code review automation work with local diffs or only GitHub pull requests?▼

Code review automation works with both local diffs and GitHub pull requests. It detects the appropriate context by coordinating git diff inspection and gh pr checkout commands to prepare the required analysis environment.

What is the best way to analyze code quality and performance in a pull request diff?▼

The best way to analyze code quality and performance in a pull request diff is to use specialized multi-agent reviewers. These agents focus on correctness, security, performance, and exploratory auditing, returning structured findings for high-confidence recommendations.

Do I need the GitHub CLI installed to review pull requests?▼

Yes, the GitHub CLI is required to review pull requests. The code review process coordinates gh pr checkout and view commands to fetch pull request context and prepare the diff analysis environment.

Related Skills

Explore More Software Engineering Skills→
webdevtodayjasonwebdevtodayjason

github-code-review

Automate code review on GitHub repositories via API or gh CLI.

Community
Advanced
narusenianarusenia

pr-comment

Post PR review findings as GitHub inline comments.

Community
Advanced
yanochka11yanochka11

github-code-review

Review GitHub pull requests and local git diffs for defects and security issues.

Community
Advanced
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced