skills.rest
mhawthorne
mhawthorneCOMMUNITY
Explore all skills by this author →
Website𝕏@mhawthorneGitHub

gza-code-review-interactive

Review committed changes on a feature branch against main.

11|1|Updated Jan 6, 2026
Search Tags:#automation#git#workflow#diff#ai-agent#code-review#pull-request
One-click install
npx skills add https://github.com/mhawthorne/gza --skill gza-code-review-interactive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gza-code-review-interactive
Source: https://github.com/mhawthorne/gza/tree/main/src/gza/skills/gza-code-review-interactive
Command: npx skills add https://github.com/mhawthorne/gza --skill gza-code-review-interactive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review committed changes on the current feature branch and output a structured code review.

Core Features & Use Cases

  • Generate a thorough, structured review from diffs between HEAD and main.
  • Validate branch state, detect ahead-of-main commits, and optionally post reviews to a PR with --pr.

Quick Start

Run the gza-code-review-interactive skill on a feature branch to generate the review.

Frequently Asked Questions about gza-code-review-interactive

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

FAQPage Schema
How do I generate a structured code review from a git diff?▼

To generate a structured code review from a git diff, run the skill on a feature branch with commits ahead of main. It uses an Agent-based reviewer to analyze the diff between HEAD and main and presents structured feedback.

Can I automatically post AI agent code reviews to a pull request?▼

Yes, you can post AI agent code reviews to a pull request by running the skill with the --pr flag. This optional feature posts the generated structured review directly to your PR after validating the branch state.

Does this code review tool work on the main branch?▼

No, this code review tool is designed specifically for non-main branches. It validates the branch state and requires commits to be ahead of main to generate the diff and run the review agent properly.

What is the best way to review committed changes on a feature branch?▼

The best way to review committed changes on a feature branch is to use a diff-based code review agent. This skill compares your current HEAD against main to detect ahead-of-main commits and outputs a thorough, structured review.

Why does my automated code review fail on the current branch?▼

Your automated code review may fail if the branch state validation detects no commits ahead of main. The skill requires a valid feature branch with committed changes to successfully generate the git diff and run the review process.

Related Skills

Explore More Software Engineering Skills→
haleyrchaleyrc
2

feature-merge

Squash merge feature branch commits into main with a Conventional Commit message.

Community
Intermediate
ookamiincookamiinc
1

ookami-code-review

Enforce code review standards for pull request feedback and communication.

Official
Intermediate
aporto-techaporto-tech

Ship

Automate code shipping with branch merging, tests, version bumps, commits, and pull requests.

Official
Advanced
Chikage0o0Chikage0o0
34

requesting-code-review

Request code reviews for committed Git ranges using the OpenCode task tool.

Community
Intermediate