skills.rest
akaszubski
akaszubskiCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Provide structured, constructive feedback during code reviews.

32|5|Updated Oct 19, 2025
Search Tags:#code quality#code review#best practices#feedback#collaboration#pull request#software development
One-click install
npx skills add https://github.com/akaszubski/autonomous-dev --skill code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/akaszubski/autonomous-dev/tree/main/plugins/autonomous-dev/skills/code-review
Command: npx skills add https://github.com/akaszubski/autonomous-dev --skill code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ineffective code reviews miss bugs, allow poor design, and provide unhelpful feedback, leading to lower code quality and developer frustration. This skill provides comprehensive guidelines for what to look for, how to write constructive comments, and best practices for both reviewers and authors.

Core Features & Use Cases

  • Review Checklist: A detailed checklist covering correctness, design quality, testing coverage, readability, and performance.
  • Constructive Feedback: Guidance on how to write clear, specific, and actionable comments, distinguishing between nits, suggestions, and critical issues.
  • Response Guidelines: Best practices for authors to effectively address feedback, ask clarifying questions, and propose alternative solutions.
  • Use Case: Before submitting a pull request, use this skill to self-review your code against best practices, ensuring it meets quality standards and anticipating potential reviewer comments.
  • Use Case: As a reviewer, use the provided templates to give structured and helpful feedback, accelerating the review process and improving code quality.

Quick Start

This is a knowledge skill, auto-activated by relevant keywords.

To get guidance on code review, simply ask:

"What should I look for when reviewing a pull request?" "How do I write a constructive code review comment?"

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I write constructive code review feedback that developers actually find helpful?▼

Constructive code review feedback is specific, actionable commentary that distinguishes between nits, suggestions, and critical issues. Focus on clarity and reasoning rather than tone; explain why a change matters for correctness, design, testing, readability, or performance, and offer examples or alternatives when proposing improvements.

What should I look for when reviewing a pull request?▼

Code review covers five dimensions: correctness (does it work as intended), design quality (is the architecture sound), testing coverage (are edge cases tested), readability (is it maintainable), and performance (are resources used efficiently). Use a structured checklist to evaluate each area systematically.

How can I self-review my code before submitting a pull request?▼

Self-review applies the same quality checklist to your own code before submission. Walk through correctness, design, test coverage, readability, and performance against best practices and project standards, catching issues early and reducing reviewer burden.

What's the best way to respond to code review feedback as an author?▼

Effective response to feedback involves addressing comments directly, asking clarifying questions when intent is unclear, proposing alternative solutions with reasoning, and explaining your approach. Treat feedback as collaboration, not criticism.

How do I accelerate code reviews while maintaining quality standards?▼

Structured review templates and checklists accelerate the process by standardizing what reviewers evaluate. Clear templates reduce decision fatigue and ensure consistency, allowing reviewers to focus on substantive issues rather than discovering what to check each time.

Can code review guidelines work across different types of software projects?▼

Code review principles for correctness, design, testing, readability, and performance apply broadly across projects. Guidelines adapt to project-specific standards and documentation, making them flexible for different codebases while maintaining core quality criteria.

Related Skills

Explore More Software Engineering Skills→
7a336e6e7a336e6e
1

git-workflow

Enforce standardized Git branching, commit messages, and pull request templates.

Community
Intermediate
richkuorichkuo
45

work-on-issue-loop

Automate GitHub issue implementation, pull request creation, and review feedback resolution.

Community
Advanced
aoxendine3aoxendine3

open-pr

Create pull requests with automated templates and testing checks.

Community
Intermediate
dhruvinrsonidhruvinrsoni

pair-programming

Define driver/navigator roles and manage pair programming session structure.

Community
Intermediate