skills.rest
ahgraber
ahgraberCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Review diffs and pull requests with structured, actionable feedback.

5|Updated Jan 30, 2026
Search Tags:#quality#diff#pre-commit#code-review#pull-request#review-workflow
One-click install
npx skills add https://github.com/ahgraber/skills --skill code-review-ahgraber
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ahgraber/skills/tree/main/skills/code-review
Command: npx skills add https://github.com/ahgraber/skills --skill code-review-ahgraber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured, actionable code reviews focused on correctness, bugs, style, and maintainability, especially for diffs and PR readiness.

Core Features & Use Cases

  • Thorough evaluation of correctness, edge cases, and code quality against the provided diff or patch.
  • Clear, actionable feedback covering correctness, style, maintainability, and risk.
  • A defined workflow for pre-commit and pre-merge reviews, including steps to collect changes, summarize impact, and document issues.

Quick Start

Review the current staged changes and provide a structured, actionable feedback focused on correctness, readability, and risk.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable code review feedback on a git diff before committing?▼

To get actionable code review feedback on a git diff, provide your staged changes or branch diffs for evaluation. The review identifies correctness, style, and maintainability issues, returning structured feedback to improve your pre-commit code quality.

What is the best way to check pull request readiness for a feature branch?▼

The best way to check pull request readiness is applying a structured review workflow to your feature branch diff. This process evaluates edge cases and code quality, documenting issues and summarizing impact to ensure your pre-merge changes are correct.

Can I use an automated review workflow for both small fixes and larger refactors?▼

Yes, you can use this review workflow for both small fixes and larger refactors. It evaluates code quality and risk across diffs, providing guidance and a standardized template to document issues regardless of the change scale.

How does a structured code review process identify bugs in staged changes?▼

A structured code review process identifies bugs in staged changes by thoroughly evaluating correctness and edge cases against the provided diff. It documents potential risks and generates clear, actionable feedback to prevent issues before merging.

What steps are needed to document issues found during a pre-merge code review?▼

To document issues found during a pre-merge code review, apply the standardized feedback template to collect changes, summarize impact, and record correctness problems. This workflow ensures actionable feedback is structured for maintainability.

Related Skills

Explore More Software Engineering Skills→
detorresramosdetorresramos
3

catching-up

Summarize current branch code changes relative to the base branch.

Community
Intermediate
lava-chenlava-chen
1

code-review

Evaluate source changes for correctness, security, performance, and maintainability issues.

Community
Intermediate
julianobarbosajulianobarbosa
7

reviewing-code

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

Community
Advanced
LLM-Dev-OpsLLM-Dev-Ops
1

github-code-review

Automate GitHub pull request reviews with multi-agent swarm analysis.

Official
Advanced