skills.rest
OpenHands
OpenHandsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-review

Review pull requests for security, readability, and correctness issues.

134|67|Updated Nov 24, 2025
Search Tags:#code quality#testing#code review#pull request#security#readability
One-click install
npx skills add https://github.com/OpenHands/extensions --skill code-review-openhands
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/OpenHands/extensions/tree/main/skills/codereview
Command: npx skills add https://github.com/OpenHands/extensions --skill code-review-openhands

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential bugs, security vulnerabilities, and areas for improvement in readability and maintainability.

Core Features & Use Cases

  • Automated Code Analysis: Scans code for common security flaws, bugs, and style issues.
  • Actionable Feedback: Provides specific line-by-line suggestions for improvement.
  • Use Case: When a developer submits a pull request, this Skill can be invoked to provide an initial review, flagging critical issues before a human reviewer steps in.

Quick Start

Use the code-review skill to analyze the changes in the current pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for security vulnerabilities and readability in pull requests?▼

Automated code review scans pull request changes to identify unsanitized input, hardcoded secrets, and complex logic, providing line-by-line actionable feedback to enhance security, readability, and correctness.

What specific code quality and security issues are flagged during a pull request review?▼

A pull request review flags security vulnerabilities like unsanitized input and hardcoded secrets, alongside code quality issues such as complex logic, poor readability, and inadequate test coverage.

Do I need to provide project structure and code changes to get actionable code review feedback?▼

Yes, providing the context of code changes and the overall project structure is required to perform structured code reviews and generate specific, actionable feedback on security and correctness.

What's the best way to catch hardcoded secrets and inadequate test coverage before human review?▼

Using automated code analysis before human review catches hardcoded secrets and inadequate test coverage by scanning code changes for common security flaws and style issues, providing actionable feedback.

Can automated code analysis replace human reviewers for checking code correctness?▼

Automated code analysis cannot fully replace human reviewers; it serves as an initial review step to flag critical security, readability, and correctness issues before a human reviewer steps in.

Related Skills

Explore More Software Engineering Skills→
zerwizzerwiz

github-code-review

Review git diffs and pull requests for defects and quality issues.

Community
Advanced
daymadedaymade
1.3k

repomix-safe-mixer

Scan codebases for hardcoded credentials and block repomix packaging when detected.

Community
Intermediate
gkganesh12gkganesh12
1

gk-review

Audit source code against documentation and test suites for architectural drift.

Community
Advanced
wutongciwutongci
8

security

Identify OWASP Top 10 security vulnerabilities in code and configurations.

Community
Advanced