code-review

Analyze the latest git diff for security and quality issues.

24|5|Updated Feb 8, 2026

Search Tags:#security #maintainability #quality #vulnerabilities #static-analysis #code-review #git-diff

Ready to run

npx skills add https://github.com/Luohaothu/everything-codex --skill code-review-luohaothu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Luohaothu/everything-codex/tree/main/skills/code-review
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill code-review-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers spend time reviewing diffs and identifying defects; this skill guides consistent, thorough reviews focused on changes to improve quality and security.

Core Features & Use Cases

Review the latest diffs (git diff) and highlight issues in modified files
Prioritize findings by severity and propose concrete fixes
Enforce best practices for security, reliability, and maintainability across codebases

Quick Start

Review the latest commit diff to identify critical issues and actionable 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 a git diff for security vulnerabilities and code quality issues?▼

To review a git diff for security vulnerabilities, analyze modified files to detect hardcoded credentials, input validation flaws, and insecure dependencies, then output structured issue guidance prioritized by severity with concrete fixes.

What is static analysis for code maintainability and how does it enforce best practices?▼

Static analysis for code maintainability evaluates modified files against best practices by calculating maintainability metrics and enforcing reliability checks to ensure consistent quality across the codebase.

Can I use automated code review to catch hardcoded credentials in my latest commit?▼

Yes, automated code review can catch hardcoded credentials in your latest commit by analyzing the git diff, focusing strictly on modified files, and flagging sensitive data exposure as a prioritized security concern.

Does this code review approach work without external dependencies or static analysis tools?▼

Yes, this code review approach works without external dependencies, operating entirely without additional static analysis tools to analyze git diffs and enforce security checks for hardcoded credentials and maintainability metrics.

What's the best way to identify insecure dependencies and input validation flaws in modified files?▼

The best way to identify insecure dependencies and input validation flaws in modified files is to run a focused review on the latest git diff, prioritizing security concerns and generating actionable fixes.