requesting-code-review

Dispatch a code-reviewer agent to analyze a git diff range and classify findings.

30|2|Updated Mar 3, 2022
One-click install
npx skills add https://github.com/lie5860/ak-guess --skill requesting-code-review-lie5860
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lie5860/ak-guess/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/lie5860/ak-guess --skill requesting-code-review-lie5860

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents regressions and missed issues by providing a repeatable, focused code review workflow that evaluates recent changes before they are merged, ensuring quality, safety, and alignment with requirements.

Core Features & Use Cases

  • Structured review template that guides reviewers to report findings as Critical, Important, or Minor with file:line references and remediation guidance.
  • Git-range analysis workflow where reviewers inspect a BASE_SHA..HEAD_SHA diff and validate implementation against plans or requirements.
  • Use Case: After finishing a feature or bugfix, dispatch the reviewer to catch architecture flaws, missing tests, or security issues before merging to main.

Quick Start

Dispatch the code-reviewer sub-agent with BASE_SHA, HEAD_SHA, WHAT_WAS_IMPLEMENTED, and PLAN_OR_REQUIREMENTS to generate a prioritized, file-referenced review.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate a structured code review for a git pull request?▼

Automate a structured code review by dispatching a code-reviewer agent with a specific git diff range (BASE_SHA..HEAD_SHA), a description of what was implemented, and a review template to classify findings by severity.

Can I enforce a review template that categorizes findings by severity with file references?▼

Yes, you can enforce a review template that classifies findings into Critical, Important, and Minor categories, requiring specific file:line references and remediation guidance for each identified issue.

What information do I need to provide to analyze a git diff range for code quality?▼

To analyze a git diff range, you must provide the BASE_SHA..HEAD_SHA commit range, a succinct description of what was implemented, and the plan or requirements to validate architecture, correctness, and tests.

Does this code review workflow support checking architecture and missing tests before merging?▼

Yes, the code review workflow supports checking architecture, missing tests, security issues, and documentation by validating the implementation against the provided plans or requirements before merging.

When should I use an automated code reviewer instead of manual pull request checks?▼

Use an automated code reviewer when you finish a feature or bugfix and need a repeatable, focused workflow to catch regressions, architecture flaws, or missed issues before merging to main.