code-review

Review code for quality, security, and maintainability issues.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill code-review-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/hafidzlvm/opencode/tree/main/.dsh/skills/code-review
Command: npx skills add https://github.com/hafidzlvm/opencode --skill code-review-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing code for defects, security vulnerabilities, and maintainability concerns is time-consuming and inconsistent, especially when reviewers lack a structured checklist. ## Core Features & Use Cases - Quality Review: Examines code for readability, structure, and adherence to maintainability best practices. - Security Analysis: Identifies potential security weaknesses and risky patterns in the reviewed code. - Use Case: A developer finishes a feature branch and invokes /code-review with the changed files to receive structured feedback on quality, security, and maintainability before opening a pull request. ## Quick Start Invoke /code-review and provide the code or changes you want reviewed for quality, security, and maintainability feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code for security vulnerabilities?▼

Invoke the code-review command with the code or files you want examined. The review covers security weaknesses alongside quality and maintainability, returning structured findings you can act on before merging.

How to check code quality before a pull request?▼

Run /code-review against your changed files or diff before opening the pull request. It evaluates readability, structure, and maintainability so you can address issues early in the review cycle.

What does a code review skill check for?▼

It checks three dimensions: code quality, security, and maintainability. The review is driven by the instructions in the underlying command file and accepts arguments to scope what gets reviewed.

Can I review only specific files or changes?▼

Yes. Any text you provide after the /code-review invocation is treated as arguments, so you can name specific files, diffs, or areas of concern to narrow the review scope.

What are the limitations of automated code review?▼

Automated review cannot fully judge business logic correctness, architectural fit, or context-specific requirements. Use it as a first-pass check and complement it with human review for critical changes.