AI Agent Hub
Back to skills
💻

Code Review Helper

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_84cc09f2/codereview-helper-yunjinh.

About this skill

Problem

Code review often gets stuck on two costs: manually reading diffs is slow, while generic linters only catch surface-level style issues. Code Review Helper targets PRs or local changes in multilingual projects, focusing review on code standards, security vulnerabilities, performance issues, and potential bugs so engineers can decide more quickly whether a change is ready to merge.

How It Works

The skill analyzes code changes and supports Python, JavaScript, TypeScript, Go, Rust, and Java. It can work with Git Diff input and evaluate issues with surrounding context instead of returning generic advice. Typical output includes:
- Style issues: naming, structure, readability, and consistency risks;
- Security and performance: potential vulnerabilities, resource usage, and inefficient implementations;
- Optimization suggestions: actionable fixes and example code where useful.
It also performs complexity analysis to help determine whether functions, control flow, or dependencies are growing too large.

Boundaries

It is best treated as a review aid, not a compiler, full static security scanner, or CI gate. Complex business logic, framework conventions, and internal standards still require repository context and human confirmation. For large diffs, missing context, or specialized language ecosystems, split the review by module and avoid treating one-pass suggestions as the final verdict.

Use Cases

  • Review Python and Go PR diffs before merge to catch bugs, security flaws, and performance risks.
  • Check TypeScript service API changes for naming, structure, and complexity issues.
  • Review local Rust or Java commits to get actionable fixes and example code before pushing.
  • Break a large Git Diff into modules and inspect resource use, inefficiency, and complexity growth.

Best For

  • Backend engineers reviewing multilingual PRs who want to catch security, performance, and complexity issues before merge.
  • Full-stack engineers maintaining TypeScript services who need style checks converted into actionable fixes.
  • Engineers taking over legacy Java or Rust projects who want fewer bugs and rework before committing.
  • Engineering leads doing Git Diff review who need checks beyond style, including security and performance.