code-review

Identify performance, concurrency, security, and readability issues in Go code.

3|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/unix2dos/skills --skill code-review-unix2dos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/unix2dos/skills/tree/main/code-review
Command: npx skills add https://github.com/unix2dos/skills --skill code-review-unix2dos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

本技能帮助 Go 代码审查,聚焦性能、并发安全、可读性和安全性等核心维度,减少潜在缺陷与技术债。

Core Features & Use Cases

  • 性能评估与热点识别,帮助定位内存分配、热路径和缓存策略中的瓶颈。
  • 并发安全审查,覆盖锁竞争、死锁风险、goroutine 生命周期与共享状态保护。
  • 安全性检查,评估输入验证、认证授权边界、敏感数据处理与潜在注入风险。
  • 可读性与可维护性提升,关注命名表达力、错误处理一致性、日志与可观测性。

Quick Start

请将要审查的 Go 文件或差异提交给审查,输出包含问题和改进建议的报告。

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review Go code for performance bottlenecks and memory allocation issues?

To review Go code for performance issues, submit your specific files or diffs to identify memory allocations, hot paths, and cache strategy bottlenecks. It outputs structured recommendations to help optimize core performance dimensions.

How do I check my Go code for concurrency safety and deadlock risks?

Checking Go code for concurrency safety involves reviewing goroutine lifecycles, lock contention, and shared state protection to identify deadlock risks. Submit your current changes to receive severity-labeled findings on these concurrency issues.

Can I use a git diff to review only the current Go code changes?

Yes, you can use a git diff to review only current Go code changes. The review applies directly to the provided diffs to output structured recommendations and severity-labeled findings specifically for your new modifications.

What is the best way to find security vulnerabilities in Go code?

The best way to find security vulnerabilities in Go code is to evaluate input validation, authentication boundaries, and sensitive data handling. Submitting your files helps identify potential injection risks and outputs actionable security findings.

Does Go code review for readability check error handling and naming conventions?

Yes, Go code review for readability checks error handling consistency, naming expressiveness, logging, and observability. Submitting your code evaluates these maintainability factors to reduce potential technical debt and improve readability.

Why does my Go code review output structured recommendations and severity labels?

Your Go code review outputs structured recommendations and severity labels to support automation integration. This format systematically categorizes performance, concurrency, security, and readability findings for immediate automated processing.