code-reviewer

Review code changes for production readiness and classify defects by severity.

2|Updated Apr 23, 2026

Search Tags:#testing #software engineering #code review #pull request #security #production readiness

Ready to run

npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill code-reviewer-gajjalaashok75-ui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/gajjalaashok75-UI/GakrCLI/tree/main/assets/skills/code-reviewer
Command: npx skills add https://github.com/gajjalaashok75-UI/GakrCLI --skill code-reviewer-gajjalaashok75-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate code changes before they reach production, reducing bugs, security risks, and avoidable rework. It turns review feedback into a structured workflow so teams can make faster, safer decisions.

Core Features & Use Cases

Production-focused review: Assess code quality, architecture, testing, and deployment readiness.
Risk triage: Separate critical defects from important fixes and minor improvements.
Feedback handling: Interpret reviewer comments carefully, verify them against the codebase, and respond with technical clarity.
Use case: Before merging a pull request, use this Skill to check the implementation against requirements, identify missing tests, and flag security or compatibility issues.

Quick Start

Ask the code review skill to review my recent changes for production readiness and summarize the critical, important, and minor issues.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I review code changes for production readiness?▼

Reviewing code for production readiness involves assessing code quality, architecture, and testing to identify defects and security risks. It applies structured severity classification to separate critical issues from minor improvements before merging.

What is the best way to triage risks during a pull request review?▼

The best way to triage risks during a pull request review is to apply structured severity classification. This separates critical defects requiring immediate fixes from important bugs and minor quality improvements, enabling faster and safer merge decisions.

How do I verify and respond to code review feedback accurately?▼

To verify code review feedback accurately, interpret reviewer comments carefully and check them against the actual codebase. Respond with technical clarity, ensuring that feedback handling validates the flagged issues before applying any suggested rework.

Can I use this to check for missing tests before merging a pull request?▼

Yes, you can evaluate testing completeness before merging a pull request. The review process includes testing evaluation to identify missing test cases and verify that the implementation meets the specified software engineering requirements.

Does automated code review work for architecture assessment?▼

Automated code review works for architecture assessment by evaluating code quality and structural decisions across modern software projects. It checks the implementation against architectural requirements to identify potential defects and quality gaps before deployment.

What are the limitations of pre-merge validation for security risks?▼

Pre-merge validation for security risks is limited to identifying known vulnerability patterns and compatibility issues within the submitted changes. It cannot detect external infrastructure threats or zero-day exploits that exist outside the provided codebase.