review-code

Analyze code changes for security, performance, and maintainability impacts.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill review-code-generaljerel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/review-code
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill review-code-generaljerel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates thorough, senior-level code reviews when users request code quality assessments, PR reviews, or change evaluations.

Core Features & Use Cases

  • Comprehensive analysis across security, performance, correctness, and maintainability.
  • Context-aware reviews that reference repository conventions, architecture notes, and testing standards.
  • Use Case: You want to review a PR; the tool analyzes changes, highlights risks, suggests improvements, and documents rationale.

Quick Start

Ask the Skill to review a specific file, PR, or branch by providing its path or identifier, and receive a structured senior-engineer review.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review a PR for security, performance, and maintainability impacts?

To review a PR for security, performance, and maintainability impacts, provide the PR diff or file path. The review identifies code changes, adapts analysis depth to the change type, and returns actionable findings with rationale.

Can I automate a senior-level code review for file edits and branch changes?

You can automate a senior-level code review for file edits and branch changes by requesting a code quality assessment. The analysis evaluates correctness and maintainability, adapting its depth to the specific project conventions provided.

Do I need project conventions and architecture references to perform a static code analysis?

Project conventions and architecture references are required to perform this static code analysis. Supplying these coding standards allows the review to be context-aware, ensuring suggestions align with your repository's specific testing and structural guidelines.

What is the best way to evaluate code quality risks in a pull request?

The best way to evaluate code quality risks in a pull request is to analyze the changes against repository conventions and testing standards. This highlights risks across security and performance, and documents improvement suggestions with clear rationale.

How does context-aware code review adapt its depth to different change types?

Context-aware code review adapts its depth to different change types by evaluating the impact of file edits, PR diffs, and branch changes against your project conventions. It then returns structured, actionable findings tailored to that specific scope.