code-review

Name: code-review
Availability: InStock
Author: arth

Review code changes for bugs, regressions, and implementation risks.

1|Updated Apr 19, 2026

Search Tags:#code review #commits #pull requests #bugs #diffs #regressions

Ready to run

npx skills add https://github.com/arthtyagi/onloop --skill code-review-arthtyagi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/arthtyagi/onloop/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/arthtyagi/onloop --skill code-review-arthtyagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect code changes before they merge so you can catch bugs, regressions, and risky implementations early.

Core Features & Use Cases

Change Review: Evaluates uncommitted diffs, commits, branches, and pull requests.
Bug Detection: Focuses on logic errors, edge cases, security issues, and broken error handling.
Context-Aware Feedback: Reads the modified files in full so findings reflect surrounding code and project conventions.
Use Case: Ask it to review a PR and return only the issues that are likely to matter to maintainers or users.

Quick Start

Use this skill to review the specified diff, commit, branch, or pull request and return concise, actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review code changes in a pull request for bugs and regressions?▼

To identify bugs in uncommitted diffs, evaluate the complete changed files to check logic, security, and error handling against repository conventions. This approach catches regressions and implementation risks before changes ship.

Does code review work with uncommitted diffs or only committed branches?▼

Code review works with both uncommitted diffs and committed branches. It evaluates pull requests, commits, and uncommitted changes to provide context-aware feedback based on the surrounding code and project conventions.

What is the best way to catch security issues and edge cases before merging code?▼

The best way to catch security issues and edge cases before merging code is to read the full changed files and validate logic and error handling. This context-aware method reports findings likely to impact maintainers.

How do I check repository conventions when reviewing a commit?▼

To check repository conventions when reviewing a commit, read the modified files in full to ensure the new logic aligns with existing project patterns. This validates that changes do not introduce broken error handling or regressions.

Can I get concise feedback on implementation risks in my code changes?▼

You can get concise feedback on implementation risks by reviewing the specified diff, commit, or pull request. The review focuses on logic errors, security issues, and edge cases to return actionable findings to maintainers.