code-review

Analyze git changes to identify critical and high-priority issues.

2|Updated Sep 11, 2025

Search Tags:#automation #git #metrics #code-review #pull-request #change-analysis

Ready to run

npx skills add https://github.com/kinneyyan/prompts --skill code-review-kinneyyan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kinneyyan/prompts/tree/main/skills/code-review
Command: npx skills add https://github.com/kinneyyan/prompts --skill code-review-kinneyyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, bc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates code review by analyzing git changes to identify critical and high-priority issues.

Core Features & Use Cases

Change analysis: Detects changes in tracked, staged, and untracked files and categorizes issues.
Automated reporting: Produces structured review outputs highlighting CRITICAL, HIGH PRIORITY, and SUGGESTIONS.
Metrics collection: Runs a metrics script to gather repository statistics and maintain a local record of review outcomes.

Quick Start

Use the code-review skill to automatically review the current git changes and generate a summarized report, then collect metrics for the session.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review for git changes before a pull request?▼

Automating code review for git changes involves analyzing tracked, staged, and untracked files to categorize issues. This process identifies critical and high-priority problems, producing a structured report for your pull request.

What is the best way to collect metrics from local code reviews?▼

Collecting metrics from local code reviews is done by running a metrics script that gathers repository statistics. This maintains a local record of review outcomes, helping you track critical issues and high-priority suggestions over time.

Do I need Bash and git installed to analyze pull request changes?▼

Yes, you need Bash and git installed to analyze pull request changes. The automated review process relies on git to detect changes and Bash to execute the scripts required for generating structured reports and collecting metrics.

Can I categorize untracked files in my automated change analysis?▼

Yes, you can categorize untracked files in your automated change analysis. The review process detects changes across tracked, staged, and untracked files, categorizing them into critical, high-priority, and suggestion levels.

Why does my automated code review produce a structured report?▼

Automated code review produces a structured report to highlight critical, high-priority, and suggestion-level issues identified in your git changes. This structured output ensures you can systematically address the most severe problems first.