code-review

Review code changes for security, quality, and maintainability issues.

Updated Apr 10, 2026

Search Tags:#git #code review #security #maintainability #quality #severity

Ready to run

npx skills add https://github.com/lpjhelder/kronon-forge --skill code-review-lpjhelder

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates comprehensive code reviews, identifying security, quality, and maintainability issues and providing severity‑rated feedback to improve code before merging.

Core Features & Use Cases

Automated Issue Detection: Scans changed files for security vulnerabilities, code quality problems, performance bottlenecks, and best‑practice violations.
Severity Rating: Classifies findings as CRITICAL, HIGH, MEDIUM, or LOW with clear recommendations.
Approval Guidance: Produces an overall recommendation to approve, request changes, or comment.
Use Cases: Review pull requests, large feature implementations, or any code change where quality assurance is required.

Quick Start

Use the code-review skill to evaluate the latest changes in the repository.

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 a git pull request?▼

Automate code review by analyzing git diff output to detect security vulnerabilities, quality problems, and maintainability issues. The review generates severity-rated reports with file:line locations and fix recommendations to guide pull request approval decisions.

What is severity rating in code review and how does it work?▼

Severity rating in code review classifies detected issues as CRITICAL, HIGH, MEDIUM, or LOW. It works by evaluating security vulnerabilities, performance bottlenecks, and best-practice violations, then mapping each finding to a severity level with clear fix recommendations.

Can I use automated code review for large feature implementations?▼

Yes, automated code review applies to major feature implementations in software projects. It evaluates changed files for security vulnerabilities, code quality problems, and best-practice violations, providing an overall recommendation to approve, request changes, or comment.

What's the best way to check code maintainability before merging?▼

The best way to check maintainability before merging is running a comprehensive code review on changed files. It identifies maintainability issues, assigns severity ratings, and provides fix recommendations with precise file:line locations to ensure code quality before approval.

Does automated code review work without external dependencies?▼

Yes, automated code review works without external dependencies. It operates independently to scan changed files identified via git diff, pull requests, or feature implementations, generating severity-rated issue reports and approval guidance.

When should I not rely on automated code review?▼

You should not rely solely on automated code review for subjective architectural decisions or business logic validation. It is designed to detect objective security vulnerabilities, quality problems, and best-practice violations with severity ratings, complementing but not replacing human judgment.