review-code

Review Go codebases and protobuf APIs across architecture, best practices, and compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured, incomplete code reviews often miss critical issues across architecture, language best practices, and API design, leading to technical debt, bugs, and maintainability problems in Go and protobuf codebases.

Core Features & Use Cases

  • Multi-domain review coverage: Analyzes code architecture (SOLID principles, design patterns, package coupling), Go best practices, and protobuf/API design (AEP compliance) in a single structured workflow.
  • Automated static analysis integration: Runs industry-standard Go tools (gocyclo, staticcheck, errcheck, nilaway) and protobuf linters (buf) to catch complexity issues, bugs, unchecked errors, and schema violations.
  • Change-aware regression detection: For PR or branch reviews, checks if current changes reintroduce historical bugs or remove critical test coverage.
  • Use Case: Use this skill when reviewing a Go service PR to catch architectural flaws, unchecked error returns, and breaking protobuf changes before merging to main.

Quick Start

Use the review-code skill to perform a full code review of the current branch's changed Go and protobuf files, including static analysis and regression risk checks.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I perform a structured code review for Go and protobuf APIs?

A structured code review for Go and protobuf APIs uses a multi-domain workflow to analyze architecture, validate Go best practices, check AEP compliance, run static analysis, and detect regression risks across changed files.

What does SOLID architecture analysis check during a Go codebase assessment?

SOLID architecture analysis during a Go codebase assessment evaluates design patterns, package coupling, and architectural boundaries to identify structural flaws and maintainability issues before they become technical debt.

How do I detect breaking protobuf schema changes and AEP compliance violations?

Detect breaking protobuf schema changes by running automated buf linting and API compliance checks against AEP standards, catching schema violations and backward-incompatible modifications before merging branches.

Can I integrate automated static analysis tools like staticcheck and gocyclo into pull request reviews?

Automated static analysis tools like staticcheck, gocyclo, errcheck, and nilaway integrate directly into pull request reviews to catch complexity issues, unchecked error returns, and potential nil panics in Go code.

What is change-aware regression detection and when do I need it for branch diff audits?

Change-aware regression detection for branch diff audits checks whether current code changes reintroduce historical bugs or remove critical test coverage, preventing regressions from reaching the main branch.

Does this code review approach work for full codebase assessments or only targeted package reviews?

This code review approach works for both full codebase assessments and targeted package or file reviews, applying architecture analysis, Go best practice validation, and protobuf compliance checks at any scope.