code-review

Analyze code changes for defects, vulnerabilities, and performance issues.

2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/MC-2 --skill code-review-maslennikov-ig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/maslennikov-ig/MC-2/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/maslennikov-ig/MC-2 --skill code-review-maslennikov-ig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential bugs, security vulnerabilities, performance issues, and areas for architectural improvement, thereby reducing risks and enhancing overall code quality.

Core Features & Use Cases

  • Automated Analysis: Scans code changes against predefined quality gates and best practices.
  • Structured Reporting: Generates detailed markdown reports with specific findings and actionable recommendations.
  • Task Integration: Creates tasks in issue tracking systems (like Beads) for remediation.
  • Use Case: Before merging a new feature, use this Skill to perform a thorough review of all modified files, ensuring no critical bugs or security flaws are introduced.

Quick Start

Use the code-review skill to analyze the staged changes in the current branch.

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 merging?

To automate code review for git changes, analyze staged commits against quality gates like type-checking and builds. This process identifies defects and security vulnerabilities, generating structured markdown reports with specific file:line references for remediation.

What is structured code review reporting and how does it track bugs?

Structured code review reporting generates detailed markdown files containing evidence-based findings for bug detection and security flaws. It creates tracking tasks in issue systems like Beads, ensuring architectural weaknesses are linked directly to specific code references.

Can I run pre-commit checks to detect security vulnerabilities and performance bottlenecks?

Yes, you can run pre-commit checks to detect security vulnerabilities and performance bottlenecks. The review depth adapts to the scope, scanning modified files against best practices to ensure no critical flaws are introduced before merging.

Does the code review process require git history analysis for branch reviews?

Yes, branch reviews require git history analysis to evaluate code changes accurately. Analyzing commit history alongside quality gate checks ensures a thorough assessment of architectural weaknesses and performance issues across the entire branch scope.

What's the best way to scan code changes for architectural weaknesses and defects?

The best way to scan code changes for architectural weaknesses and defects is using an automated analysis tool. It evaluates modified files against predefined quality gates, producing actionable markdown reports with evidence-based findings and creating remediation tasks.