code-review

Identify security, performance, and correctness issues in code changes.

704|58|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/openyak/desktop --skill code-review-openyak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/openyak/desktop/tree/main/backend/app/data/plugins/engineering/skills/code-review
Command: npx skills add https://github.com/openyak/desktop --skill code-review-openyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes with a structured lens on security, performance, correctness, and maintainability.

Core Features & Use Cases

  • Structured review: evaluate diffs for security risks, performance issues, and edge-case handling.
  • Actionable guidance: provides clear, code-level recommendations and examples.
  • PR-ready outputs: summarizes findings suitable for ticketing and merges.

Quick Start

Review a PR URL or file diff to get a prioritized findings list.

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 pull request for security vulnerabilities and performance issues?

To review a pull request for security and performance issues, apply a structured code review to the diff to identify risks, evaluate edge-case handling, and generate actionable, code-level recommendations for the merge.

What is the best way to audit code changes for correctness before merging?

Auditing code changes for correctness involves evaluating touched files across repositories to detect edge-case handling failures, providing a prioritized findings list suitable for ticketing and traceable merge outcomes.

Can I use an automated code review to check diffs across multiple repositories?

Yes, you can apply automated code review to touched files across repositories, evaluating diffs for security risks and performance issues to produce PR-ready summaries and actionable code-level guidance.

How do I get actionable suggestions when reviewing a file diff?

Reviewing a file diff with structured dimensions yields actionable suggestions by identifying specific security, performance, and correctness issues, providing clear examples and prioritized findings for immediate implementation.

Does automated code review work for both security audits and performance optimization?

Automated code review works for both security audits and performance optimization by applying structured review dimensions to code changes, identifying risks, and outputting actionable guidance for both concerns simultaneously.

What are the limitations of automated diff reviews for maintainability?

While automated diff reviews identify security, performance, and correctness issues with actionable guidance, their maintainability analysis is limited to the scope of the provided code changes rather than the entire repository architecture.