skills.rest
dstanberry
dstanberryCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code changes for style, correctness, performance, security, and maintainability.

7|Updated Nov 30, 2019
Search Tags:#git#best-practices#static-analysis#quality-assurance#code-review#software-engineering#pull-requests
One-click install
npx skills add https://github.com/dstanberry/dotfiles --skill code-review-dstanberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/dstanberry/dotfiles/tree/main/ai/claude/skills/code-review
Command: npx skills add https://github.com/dstanberry/dotfiles --skill code-review-dstanberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitate consistent, high-quality code reviews by providing a structured checklist and targeted feedback on changes.

Core Features & Use Cases

  • Structured, checklist-driven review of changes across files and commits
  • Context-aware feedback with actionable improvements and references
  • Works with repositories, pull requests, and recently changed files to identify review targets

Quick Start

Provide a structured, actionable code review for the specified file(s) or the most recently changed files.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I get actionable feedback on a git pull request?▼

To get actionable feedback on a git pull request, analyze the changed files and commit messages to identify issues across style, correctness, performance, security, and maintainability with explicit suggestions.

What should a structured code review cover?▼

A structured code review should cover style, correctness, performance, security, and maintainability, providing targeted feedback with actionable improvements and references for the specified changes.

Can I review recently changed files if no specific pull request is provided?▼

Yes, you can review recently changed files if no specific pull request is provided, as the review process defaults to analyzing recent repository changes to articulate actionable feedback.

What is the best way to ensure code quality and best practices in a repository?▼

The best way to ensure code quality and best practices in a repository is applying a checklist-driven review to changed files and commits, articulating targeted feedback on correctness and maintainability.

Does static analysis feedback work without explicit review targets?▼

Static analysis feedback works without explicit review targets by defaulting to the most recently changed files in the repository, ensuring feedback on style, security, and performance is still generated.

Related Skills

Explore More Software Engineering Skills→
ebinnionebinnion
5

testing-plan-from-history

Analyze git history and PRs to generate testing instructions for changed files.

Community
Intermediate
peancharoenpeancharoen

speckit.reviewer

Review git diffs and file paths for code issues with severity labels.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
zebbernzebbern
4.5k

AWS Penetration Testing

Enumerate AWS IAM misconfigurations and privilege escalation paths.

Community
Advanced