skills.rest
OM-bit-hub
OM-bit-hubCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code diffs and pull requests for defects across eight passes.

Updated Aug 23, 2026
Search Tags:#security#quality#best-practices#code-review#diffs#review-process
One-click install
npx skills add https://github.com/OM-bit-hub/daily_tracker --skill code-review-om-bit-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/OM-bit-hub/daily_tracker/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/OM-bit-hub/daily_tracker --skill code-review-om-bit-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is essential to identify logic errors, security gaps, performance bottlenecks, and readability issues in code changes before they reach production, reducing risk and speeding up delivery.

Core Features & Use Cases

  • Structured evaluation of diffs, PRs, or changed files against correctness, security, performance, duplication, and best practices.
  • Guided workflow with step-by-step context gathering, issue identification, and actionable fixes to improve quality and maintainability.
  • Use Case: before merging a feature branch, after implementing a fix, or during teammate reviews to ensure code quality across the team.

Quick Start

Review a code change by following the eight-pass framework to identify issues and propose fixes.

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 for security and performance issues before merging?▼

A thorough code review of diffs or PRs identifies logic errors, security gaps, and performance bottlenecks before they reach production, reducing risk and speeding up delivery.

What is the best way to conduct a structured code review on a pull request?▼

Conducting a structured code review involves a guided workflow with step-by-step context gathering, eight review passes, and risk ratings to identify logic errors and propose actionable fixes.

Can I use this code review process for both frontend and backend feature branches?▼

Yes, this code review process is applicable to pull requests and feature branches across both backend and frontend codebases, evaluating logic, security, performance, and readability.

Does the code review evaluate readability and best practices, or just logic errors?▼

The code review evaluates more than just logic errors; it conducts a thorough assessment of correctness, security, performance, duplication, and readability against best practices.

When do I need to run an eight-pass code review on my diffs?▼

You need an eight-pass code review on diffs before merging a feature branch, after implementing a fix, or during teammate reviews to catch defects and ensure code quality before shipping.

Related Skills

Explore More Software Engineering Skills→
DethonDethon
3

requesting-code-review

Generate reviewer-ready summaries of code changes with task details and changed files.

Community
Basic
tusharg1993tusharg1993

review

Identify correctness, safety, performance, and compliance issues in ClickHouse PR patches.

Community
Advanced
bugrabilgebugrabilge
10

code-reviewer

Analyze code for security vulnerabilities and performance issues.

Community
Advanced
voidrotvoidrot

python-code-style

Format and lint Python source code with Black, Ruff, isort, and mypy.

Community
Advanced