skills.rest
raghavpillai
raghavpillaiCOMMUNITY
Explore all skills by this author →
Website𝕏@rag_pilGitHub

code-review

Analyze code diffs to identify critical bugs, security risks, and breaking changes.

1|Updated Aug 26, 2024
Search Tags:#performance#security#reporting#diff#bugs#static-analysis#code-review
One-click install
npx skills add https://github.com/raghavpillai/dotfiles --skill code-review-raghavpillai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/raghavpillai/dotfiles/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/raghavpillai/dotfiles --skill code-review-raghavpillai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive code review with high signal, low noise. Flags only critical issues (bugs, security, performance, breaking changes). Skips style, nits, and minor improvements. Outputs a structured report.

Core Features & Use Cases

  • Flag only high-severity issues across diffs to speed up reviews on large codebases.
  • Generate a structured report that clearly categorizes findings for developers and reviewers.
  • Works with git diffs, supports scanning for security, performance, and architectural concerns.

Quick Start

Provide a diff for review and request a thorough, structured assessment focusing on critical issues.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I flag only critical bugs and security issues in a git diff?▼

To flag critical bugs and security issues in a git diff, analyze the changes against a stable baseline. This process surfaces only high-severity risks like breaking changes while skipping style nits to ensure high signal, low noise reporting.

Does this code review approach check for performance and architectural concerns in pull requests?▼

Yes, this code review approach checks pull requests for performance and architectural concerns. It scans diffs to identify security risks, performance problems, and breaking changes, categorizing them into a structured report suitable for gatekeeping reviews.

What is the best way to generate a structured report for code changes?▼

The best way to generate a structured report for code changes is to apply static analysis to the diff. This categorizes findings into a clear taxonomy of bug, security, performance, breaking, and architecture issues for developers and reviewers.

Can I use static analysis to skip minor style nits during patch reviews?▼

Yes, you can use static analysis to skip minor style nits during patch reviews. By focusing strictly on critical issues across the provided diffs, the analysis skips style, nits, and minor improvements to speed up reviews on large codebases.

How do I categorize breaking changes when analyzing code diffs?▼

To categorize breaking changes when analyzing code diffs, apply the review against a stable baseline. The resulting structured report uses a clear taxonomy to classify findings specifically as bug, security, performance, breaking, or architecture issues.

Related Skills

Explore More Software Engineering Skills→
ToqsickToqsick

github-code-review

Analyze code diffs and generate inline comments for GitHub pull requests.

Community
Advanced
pskoettpskoett
273

simplify-and-harden-ci

Execute headless CI scans for simplification, hardening, and documentation on pull requests.

Community
Intermediate
rambozramboz
5

pr-review

Generate a four-section markdown PR review from diffs or branch changes.

Community
Intermediate
igor1309igor1309

arch-spec-review

Review architecture specifications for completeness, abstraction, and separation of concerns.

Community
Intermediate