skills.rest
hypeJunction
hypeJunctionCOMMUNITY
Explore all skills by this author →
GitHub

code-review-guidelines

Codify code review best practices with checklists and feedback labels.

1|Updated Dec 1, 2025
Search Tags:#quality assurance#code review#best practices#feedback#checklist#pull request
One-click install
npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill code-review-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-guidelines
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/code-review-guidelines
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill code-review-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive set of guidelines and best practices for conducting effective code reviews, ensuring higher code quality, consistency, and maintainability across projects.

Core Features & Use Cases

  • Review Checklist: A detailed checklist covering functionality, code quality, security, testing, and performance.
  • Comment Labels: Standardized labels ([blocking], [suggestion], [nit], [question], [praise]) for clear and actionable feedback.
  • Feedback Patterns: Examples of constructive and specific feedback to foster a positive review environment.
  • PR Size Guidelines: Recommendations for managing Pull Request size to improve review efficiency.
  • Anti-Patterns: Identification of common pitfalls to avoid during code reviews.

Quick Start

Follow the provided checklist and comment labeling system during your next code review.

Frequently Asked Questions about code-review-guidelines

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

FAQPage Schema
What should be included in a code review checklist?▼

A code review checklist should cover functionality, code quality, security, testing, and performance. It enforces consistent evaluation standards to ensure higher code quality and maintainability across software projects.

How do I categorize code review feedback?▼

Categorize code review feedback using standardized labels like blocking, suggestion, nit, question, and praise. This ensures comments are clear, actionable, and foster a constructive review environment.

What are common code review anti-patterns to avoid?▼

Common code review anti-patterns are pitfalls that hinder constructive feedback and review efficiency. Identifying these common issues helps foster a positive review environment and improves pull request quality.

What is the best way to manage pull request size for code reviews?▼

Managing pull request size involves following specific size guidelines to improve review efficiency. Smaller, well-scoped pull requests allow for more consistent and constructive code quality assurance evaluations.

How do I write constructive code review comments?▼

Write constructive code review comments by applying standardized feedback patterns and labels. Using specific examples fosters a positive environment while ensuring feedback remains actionable and clear.

Related Skills

Explore More Software Engineering Skills→
goffitygoffity

pr

Run tests, build, review code, and create a pull request with issue tracking.

Community
Advanced
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
tanjedtanjed
1

refactor

Apply automated refactoring tools to improve code structure and readability.

Community
Intermediate