code-review

Name: code-review
Availability: InStock
Author: reedmayhew18

Identify issues in code changes and produce a severity-organized report.

23|Updated Apr 5, 2026

Search Tags:#automation #git #security #quality #diff #code-review

Ready to run

npx skills add https://github.com/reedmayhew18/ClawedBack --skill code-review-reedmayhew18

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes for quality, security, and correctness. Use when the user says "review this PR", "review these changes", "check my code", "look at what I changed", or after implementing a feature. Produces a severity-organized report.

Core Features & Use Cases

Identify issues across changes with file:line references, categorized by severity (Critical > Warnings > Suggestions).
Provide actionable fix suggestions and prioritize findings.
Use Case: When reviewing a PR, generate a structured report you can present to teammates.

Quick Start

Ask the agent to review the provided diff (PR/branch) and generate a severity-graded report.

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 reviews for a git branch diff?▼

You can automate code review for a git branch diff by applying the skill to generate a severity-organized report. It analyzes the provided diff scope and outputs categorized findings with file:line references and targeted remediation suggestions.

Can I check my local commits for security and quality issues automatically?▼

Yes, you can check local commits for security and quality issues by applying the review process to your HEAD changes. It identifies issues across languages and produces a structured report categorized as Critical, Warnings, and Suggestions with actionable fixes.

What is the best way to generate a structured PR review report with severity grades?▼

The best way to generate a structured PR review report is to process the PR diff through an automated review. This categorizes findings by severity—Critical, Warnings, and Suggestions—and provides file:line references with prioritized, actionable fix suggestions to present to teammates.

Does automated code review work across multiple programming languages?▼

Automated code review works across multiple programming languages when reviewing code changes. It identifies issues in the provided diff scope and produces a severity-organized report with specific file:line references and remediation suggestions regardless of the language used.

How do I get actionable fix suggestions when reviewing a PR diff?▼

To get actionable fix suggestions when reviewing a PR diff, apply an automated review to the changes. The process prioritizes findings and outputs targeted remediation suggestions categorized by severity, helping you address Critical issues and Warnings efficiently.