review

Analyze code changes in a git range and produce prioritized review feedback.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/atmigtnca/sidep-ops --skill review-atmigtnca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/atmigtnca/sidep-ops/tree/main/skills/review
Command: npx skills add https://github.com/atmigtnca/sidep-ops --skill review-atmigtnca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review processes help ensure that changes align with requirements, maintain quality, and reduce risks before they reach production by surfacing issues early.

Core Features & Use Cases

  • Structured review prompts that guide assessment of code quality, architecture, tests, and documentation.
  • Severity-based feedback with clear remediation steps and prioritization for blockers, important, and minor issues.
  • End-to-end review workflow that can be reused for new features, bug fixes, and refactors, including guidance on merging decisions.

Quick Start

Run the review workflow against the current branch to produce a prioritized feedback report.

Frequently Asked Questions about review

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

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

Automate code review by analyzing changes within a given git range to ensure they meet requirements and project standards. The workflow evaluates code quality, tests, and architecture to provide structured, prioritized feedback before merging.

How does automated pull request review handle risk and architectural implications?

Pull request review assesses risk and architectural implications by evaluating code changes against project standards. It generates severity-based feedback that categorizes issues into blockers, important improvements, and minor guidance to ensure safe software acceleration.

Can I use automated code review for bug fixes and refactoring?

Yes, you can use this code review workflow across new features, bug fixes, and refactors. It applies a reusable end-to-end assessment process to evaluate code quality, tests, and documentation for any type of code change.

What is the best way to structure feedback from a code review?

The best way to structure code review feedback is by severity, prioritizing blocking issues first, then actionable improvements, and finally minor issues. This approach provides clear remediation steps and guidance for implementation decisions.

Does automated code review require specific dependencies to analyze a git range?

No specific dependencies are required to analyze a git range for code review. The workflow operates independently to evaluate code quality, tests, and risk within the provided changeset to produce a prioritized feedback report.