code-review

Review code changes in diffs and pull requests for bugs and edge cases.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Huddo121/My-Agent-Loop --skill code-review-huddo121
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Huddo121/My-Agent-Loop/tree/main/.cursor/skills/code-review
Command: npx skills add https://github.com/Huddo121/My-Agent-Loop --skill code-review-huddo121

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, ensuring correctness, identifying edge cases, and maintaining alignment with project-specific patterns, thereby improving overall code quality and reducing bugs.

Core Features & Use Cases

  • Correctness-focused Reviews: Prioritizes identifying bugs, errors, and potential edge cases in code.
  • File-Specific Feedback: Organizes review comments clearly by the file they pertain to.
  • Alignment with Local Patterns: Lightly considers repository conventions for consistency.
  • Use Case: When a developer submits a pull request, this Skill can provide a thorough review, flagging potential issues before they are merged.

Quick Start

Use the code-review skill to review the changes in the current pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for a pull request to catch edge cases?

Automating code review for a pull request involves analyzing code changes in diffs to identify bugs, potential errors, and edge cases. This process flags correctness issues and areas for high-impact simplification before merging.

How does a project-scoped code review align feedback with local patterns?

A project-scoped code review aligns feedback with local patterns by lightly integrating repository conventions found in AGENTS.md and docs. This ensures the automated feedback maintains consistency with your project's specific coding standards.

Can I review modified files for bugs and potential errors automatically?

Yes, you can review modified files for bugs and potential errors automatically by analyzing code changes in diffs or pull requests. The review organizes feedback clearly by the specific file it pertains to for easy tracking.

Does automated code review work without configuring external dependencies?

Automated code review works without external dependencies, relying instead on internal references and repository docs. It focuses on correctness and edge cases directly from the modified files, needing only your local codebase context to function.

What is the best way to identify high-impact simplifications in a diff?

The best way to identify high-impact simplifications in a diff is to perform a correctness-focused review that analyzes code changes against local patterns. This highlights potential errors while pinpointing areas where code can be safely simplified.

When should I not rely on automated code review for software development?

You should not rely on automated code review when a change requires deep business logic validation beyond local pattern matching, as the review focuses primarily on correctness, edge cases, and structural simplification within the diff itself.