code-review

Analyze code diffs for bugs, security risks, and maintainability issues.

Updated May 6, 2026
One-click install
npx skills add https://github.com/htayj/src --skill code-review-htayj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/htayj/src/tree/main/dotfiles/pi/.pi/agent/packages/general-dev-suite/skills/code-review
Command: npx skills add https://github.com/htayj/src --skill code-review-htayj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers and teams perform thorough code reviews focused on bugs, security issues, and maintainability, enhancing software quality before deployment.

Core Features & Use Cases

  • Bug Detection: Analyzes code diffs for correctness and potential issues.
  • Security Checks: Identifies vulnerabilities such as injection points and secrets.
  • Maintainability Analysis: Checks for consistent coding patterns and code clarity.
  • Use Case: A developer submits a pull request; this Skill reviews the changes for security flaws and code quality to prevent potential issues from reaching production.

Quick Start

Use the code-review skill to analyze the latest code diff for security vulnerabilities and bugs.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check a pull request for security vulnerabilities and bugs?

To check a pull request for security vulnerabilities and bugs, you can analyze the code diff to identify injection points, secrets, and correctness issues. This process evaluates changes against static analysis scripts and review checklists to prevent flaws from reaching production.

What does static analysis look for during a code review?

Static analysis during a code review looks for bugs, security risks, and maintainability issues within code diffs. It identifies vulnerabilities like injection points and secrets while checking for consistent coding patterns and overall code clarity.

Can I analyze code diffs for maintainability issues before merging?

Yes, you can analyze code diffs for maintainability issues before merging by checking for consistent coding patterns and code clarity. This ensures software quality is evaluated and improved before changes are deployed.

What is the best way to detect injection points and secrets in code changes?

The best way to detect injection points and secrets in code changes is to run dedicated security checks on the code diff. This identifies vulnerabilities and potential security flaws before the code is merged into the main branch.

Do I need static analysis scripts to review code quality?

Yes, you need static analysis scripts and review checklists to effectively evaluate code changes. These components help analyze code diffs for correctness, security risks, and maintainability issues during the review process.

Why should I review code changes before deployment?

You should review code changes before deployment to catch bugs, identify security vulnerabilities, and improve maintainability. This ensures software quality is enhanced and potential issues are prevented from reaching production environments.