skills.rest
ricardoquesada
ricardoquesadaCOMMUNITY
Explore all skills by this author →
Website𝕏@ricardoquesadaGitHub

code-review

Review code changes for bugs, style inconsistencies, and best practices.

163|9|Updated Dec 20, 2025
Search Tags:#quality assurance#code review#best practices#pull request#coding standards#bug detection
One-click install
npx skills add https://github.com/ricardoquesada/regenerator2000 --skill code-review-ricardoquesada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ricardoquesada/regenerator2000/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/ricardoquesada/regenerator2000 --skill code-review-ricardoquesada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify potential issues in code, ensuring higher quality, adherence to standards, and fewer bugs before deployment.

Core Features & Use Cases

  • Bug Detection: Identifies common programming errors and logical flaws.
  • Style Enforcement: Checks for adherence to project-specific coding conventions.
  • Best Practice Guidance: Offers suggestions for more efficient and maintainable code.
  • Use Case: Use this skill to review a pull request before merging to catch any potential regressions or style violations.

Quick Start

Review the provided code snippet for correctness and style.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request to catch bugs and style violations before merging?▼

To review a pull request, apply a systematic checklist covering correctness, edge cases, style, and performance. This process identifies logical flaws and style inconsistencies to ensure higher quality and fewer bugs before deployment.

What is the best way to enforce coding standards during code reviews?▼

Enforcing coding standards during a code review involves checking the provided code against project-specific conventions. This identifies style inconsistencies and offers suggestions for more efficient, maintainable code.

Can I use an automated checklist approach for bug detection in code changes?▼

Yes, using a systematic checklist approach for bug detection evaluates code changes for common programming errors and logical flaws. This ensures potential regressions are caught during quality assessments.

Does general code quality assessment require checking for edge cases and performance?▼

General code quality assessment requires checking for edge cases and performance alongside correctness. A systematic checklist approach ensures reviews cover these areas to provide best practice guidance and catch potential issues.

What are the limitations of using a checklist approach for code review?▼

A checklist approach for code review relies on evaluating provided code snippets. It targets common programming errors and style violations but may not fully replace deeper architectural evaluations or runtime testing for complex regressions.

Related Skills

Explore More Software Engineering Skills→
shuff57shuff57

caveman-review

Provide concise one-line code review comments for pull requests.

Community
Intermediate
djscrew1738djscrew1738

code-review

Review pull requests for data structure quality, security risks, and coding standards.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
outfitter-devoutfitter-dev
2

cli-testing

Run automated Navigator CLI tests with bun and navigator-server.

Official
Intermediate