code-reviewer

Reviews git diffs for correctness, security, and convention alignment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tktaf/codex --skill code-reviewer-tktaf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/tktaf/codex/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/tktaf/codex --skill code-reviewer-tktaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, ensuring correctness, security, and adherence to coding conventions with a focus on minimizing false positives.

Core Features & Use Cases

  • Automated Code Analysis: Reviews git diff output to identify potential bugs, security vulnerabilities, and style violations.
  • Low False Positive Rate: Prioritizes high-confidence findings to reduce noise for developers.
  • Use Case: Before merging a pull request, use this Skill to automatically scan the changes for critical bugs or security flaws, providing actionable feedback.

Quick Start

Use the code-reviewer skill to review the changes in the current git branch.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review git diff output for security vulnerabilities and bugs before merging?▼

To review git diff output for security vulnerabilities and bugs, analyze the code changes to identify logic errors, design fit issues, and safety concerns. This automated code analysis prioritizes high-confidence findings to minimize false positives and ensure correctness.

Can I automatically scan a pull request for convention alignment and test completeness?▼

Yes, you can automatically scan a pull request for convention alignment and test completeness. By analyzing specified file ranges or git diffs, the review process checks for style violations and ensures the code adheres to required conventions.

What is the best way to minimize false positives during automated code review?▼

The best way to minimize false positives during automated code review is to prioritize high-confidence findings. Focusing on correctness, security, and convention alignment reduces noise for developers, ensuring only actionable and critical issues are reported.

Does automated code analysis work with specific file ranges instead of the entire repository?▼

Yes, automated code analysis works with specific file ranges instead of the entire repository. You can analyze targeted file ranges or git diff outputs to report high-confidence issues, ensuring focused and efficient code quality checks.

When do I need to use an automated code reviewer for debugging and quality assurance?▼

You need to use an automated code reviewer for debugging and quality assurance before merging a pull request. It identifies potential bugs, security vulnerabilities, and style violations in the code changes, providing actionable feedback to ensure code quality.