code-reviewer

Analyze pull requests for code smells, secrets, and SOLID violations.

Updated Sep 24, 2021
One-click install
npx skills add https://github.com/coolguy1771/dotfiles --skill code-reviewer-coolguy1771
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/coolguy1771/dotfiles/tree/main/chezmoi/private_dot_cursor/skills/code-reviewer
Command: npx skills add https://github.com/coolguy1771/dotfiles --skill code-reviewer-coolguy1771

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the tedious and time-consuming process of manually reviewing code, ensuring higher quality, identifying potential risks early, and freeing up developer time.

Core Features & Use Cases

  • PR Analysis: Analyzes git diffs to assess review complexity, identify risks like hardcoded secrets, and prioritize files for review.
  • Code Quality Checks: Scans source code for common smells, SOLID principle violations, and complexity issues across multiple languages.
  • Report Generation: Consolidates findings into structured review reports with actionable insights and verdicts.
  • Use Case: When reviewing a pull request, use this Skill to get an immediate assessment of its complexity, identify critical security risks, and receive a prioritized list of files to focus on, along with a quality score.

Quick Start

Use the code-reviewer skill to analyze the current pull request for quality and risks.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for pull requests to detect security risks?

Automate code review by analyzing pull request git diffs to identify hardcoded secrets, calculate complexity, and prioritize files. This process assesses risk factors and generates a structured review report with actionable insights and a quality score.

Can I run static analysis for code smells and SOLID violations across multiple languages?

Yes, static analysis for code smells and SOLID violations supports TypeScript, JavaScript, Python, Go, Swift, and Kotlin. It scans source code to detect complexity issues and common architectural antipatterns across these languages.

Do I need Python and Git installed to analyze pull request complexity?

Yes, you need Python and Git installed to analyze pull request complexity. The automation executes Python scripts for static analysis and leverages Git to process diffs and assess review complexity for the codebase.

What is the best way to prioritize files for review when analyzing a large pull request?

The best way to prioritize files for review is by analyzing git diffs to assess complexity and identify risk factors. This generates a prioritized list of files to focus on, providing a clear quality score and actionable verdicts.

How are code review reports generated from static analysis findings?

Code review reports are generated by consolidating static analysis findings into structured formats. They leverage reference markdown files for coding standards to produce actionable insights, checklists, and overall quality verdicts.