code-review

Analyze pull request changes for defects, security concerns, and improvement opportunities.

Updated Feb 26, 2023
One-click install
npx skills add https://github.com/burakergun394/projects --skill code-review-burakergun394
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/burakergun394/projects/tree/main/FollowCatcher/.claude/skills/code-review
Command: npx skills add https://github.com/burakergun394/projects --skill code-review-burakergun394

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are often time-consuming and inconsistent; this Skill standardizes thorough reviews and provides actionable feedback to PRs and changes.

Core Features & Use Cases

  • Structured feedback: identify correctness, security, maintainability, and performance issues.
  • PR guidance: review pull requests, guide changes, and produce prioritized remediation steps.
  • Context-aware analysis: suitable for .NET/C# projects and multi-language codebases.

Quick Start

Review a PR by analyzing the changes for correctness, security, and maintainability, and return actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I analyze code changes in a pull request for defects?

To analyze code changes in a pull request, review the diffs to identify correctness issues, security vulnerabilities, and maintainability concerns. This process evaluates software quality by applying structured analysis to produce actionable, prioritized remediation steps.

Can I use code review for .NET and C# projects?

Yes, you can use code review for .NET and C# projects. The context-aware analysis supports multi-language codebases, allowing you to evaluate software quality, identify defects, and guide changes effectively across common software-review scenarios.

What is the best way to standardize pull request evaluations across a team?

The best way to standardize pull request evaluations is to apply a structured code review process that categorizes feedback into correctness, security, maintainability, and performance. This ensures consistent software quality checks and prioritized guidance for every change.

How do I check my code for security vulnerabilities before merging?

To check code for security vulnerabilities before merging, run a static code review analysis on your pull request. This identifies security concerns and other defects within the code changes, providing actionable feedback to ensure software quality before integration.

What types of issues does static analysis identify during a code review?

Static analysis during a code review identifies correctness defects, security vulnerabilities, maintainability issues, and performance bottlenecks. It analyzes pull request changes to deliver structured, actionable feedback that improves overall software quality.