Code Reviewer

Fetch GitHub PR metadata and diffs, assess issues by priority, and generate review comments.

Updated Aug 15, 2023
One-click install
npx skills add https://github.com/connectwithprakash/dotfiles --skill code-reviewer-connectwithprakash
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code Reviewer
Source: https://github.com/connectwithprakash/dotfiles/tree/main/.claude/skills/github-code-reviewer
Command: npx skills add https://github.com/connectwithprakash/dotfiles --skill code-reviewer-connectwithprakash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers provide thoughtful, actionable feedback on PRs, helping authors improve quality and reduce cycle time.

Core Features & Use Cases

  • Systematic review: inspect changed files, assess correctness, security, performance, and maintainability.
  • Prioritized feedback: categorize issues by severity and propose concrete fixes.
  • Documentation & testing cues: suggest tests and documentation improvements as part of the review.

Quick Start

Review PR #123 and provide inline comments, a summary, and suggested tasks or issues for follow-up.

Frequently Asked Questions about Code Reviewer

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

FAQPage Schema
How do I provide constructive feedback on pull requests?

Constructive PR feedback systematically reviews changed files for correctness, security, performance, and maintainability, then prioritizes issues by severity with concrete fixes and actionable suggestions to help authors improve code quality.

What should I look for when reviewing code changes?

Code review assesses security vulnerabilities, performance bottlenecks, correctness of logic, maintainability concerns, and compliance with standards. Feedback categorizes findings by priority (P0–P3) and proposes concrete fixes for each issue.

Can I automate code review for GitHub pull requests?

Yes, automated code review fetches PR metadata and diffs, assesses issues across security, performance, correctness, and maintainability categories, generates inline and file-level comments, and formats output for posting via GitHub review APIs.

How do I structure feedback to reduce PR cycle time?

Effective PR feedback combines inline comments at specific code locations, file-level summaries, prioritized issue lists, and suggested follow-up tasks or documentation improvements, enabling authors to address concerns efficiently.

What's the best way to identify security issues in code diffs?

Security-focused code review examines changed files against known vulnerability patterns, assesses risk exposure, and flags issues by priority. Reviewers provide inline comments with concrete remediation steps for each security concern.

Should I suggest tests and documentation as part of code review?

Yes, comprehensive code review includes cues for test coverage gaps and documentation improvements alongside correctness and security feedback, helping authors deliver more maintainable and verifiable code.