code-review

Review git diffs for security, quality, performance, and maintainability issues.

28|5|Updated Jan 26, 2026

Search Tags:#git #security #maintainability #quality #best-practices #code-review #severity

Ready to run

npx skills add https://github.com/MeroZemory/oh-my-droid --skill code-review-merozemory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/MeroZemory/oh-my-droid/tree/main/skills/code-review
Command: npx skills add https://github.com/MeroZemory/oh-my-droid --skill code-review-merozemory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents low-quality or vulnerable code from entering the main branch by examining every change for security, performance, and maintainability regressions before approval.

Core Features & Use Cases

Deep Druid Analysis: Delegation to the Claude Opus code-reviewer agent inspects the git diff or selected files for nuanced risks.
Severity-Tiered Feedback: CRITICAL, HIGH, MEDIUM, and LOW labels with file:line evidence guide prioritization and action.
Actionable Reporting: Each issue includes a concrete fix recommendation, context-specific guidance, and a final approval verdict to inform merge decisions.
Use Case: Run it as part of every pre-merge checklist or after major feature work so teams ship confident, resilient releases.

Quick Start

Ask the code-review skill to analyze the current git diff and flag security, quality, performance, and maintainability issues.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I run a security and quality code review on a git diff before merging?▼

A code review on a git diff inspects changes for security, performance, and maintainability issues. It provides severity-rated findings with file:line locations, concrete fixes, and an approval recommendation to validate changes before merging.

What does a comprehensive code review cover for pull request scenarios?▼

A comprehensive code review covers security vulnerabilities, quality regressions, performance bottlenecks, and maintainability issues. It provides severity-tiered feedback with file:line evidence to guide prioritization and merge decisions.

How are code review findings prioritized for bug and security risks?▼

Code review findings are prioritized using CRITICAL, HIGH, MEDIUM, and LOW severity labels. These tiers guide action by highlighting the most urgent security and bug risks alongside their specific file:line locations.

When should I perform a pre-merge code review on my feature branch?▼

Perform a pre-merge code review as part of every pre-merge checklist or after major feature work. This validates changes, catches security risks early, and ensures teams ship confident, resilient releases.

Does automated code review provide an approval recommendation for pull requests?▼

Yes, automated code review provides a final approval verdict to inform merge decisions. Each identified issue includes a concrete fix recommendation and context-specific guidance to help teams confidently validate changes before merging.

What is the best way to catch maintainability regressions in a pull request?▼

The best way to catch maintainability regressions is to perform a comprehensive code review on the git diff before approval. This process inspects changes for nuanced risks and provides actionable, severity-rated feedback.