go-code-review

Review Go diffs with severity-labeled findings and rule citations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review Go changes before they ship, so you can catch correctness, style, security, concurrency, and testing issues early instead of discovering them after merge.

Core Features & Use Cases

  • Systematic diff review: Walks Go changes file by file and checks formatting, errors, naming, declarations, control flow, functions, interfaces, concurrency, data structures, logging, imports, generics, and tests.
  • Severity-based findings: Labels issues as must-fix, should-fix, or nit so reviewers can prioritize what blocks merge.
  • Community-standard guidance: Anchors feedback in Go best practices and community rules, making reviews consistent and actionable.
  • Use case: Review a pull request for a Go service and return line-specific findings with clear rule citations and severity labels.

Quick Start

Ask the skill to review your Go pull request diff and return only line-referenced findings grouped by severity.

Frequently Asked Questions about go-code-review

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

FAQPage Schema
How do I review a Go pull request for concurrency and interface issues?

Reviewing a Go pull request involves walking the diff to check formatting, linting, concurrency, and interface design. This ensures you catch correctness issues and apply community style standards consistently before merging code changes.

What is the best way to enforce Go community style and linting standards before merge?

Enforcing Go style requires anchoring diff feedback in community best practices during pre-release checks. This validates formatting and linting changes consistently by providing line-specific findings with severity labels and rule-based citations.

Can I use automated code review to check Go 1.21 projects for testing and logging flaws?

Yes, you can check Go 1.21+ projects for testing and logging flaws during pre-release checks. The review applies to pull requests and returns line-specific findings grouped by severity to help reviewers prioritize must-fix issues.

How do I label Go code review findings by severity to prioritize pull request fixes?

Label Go code review findings as must-fix, should-fix, or nit to prioritize pull request fixes. This severity labeling helps reviewers distinguish blocking correctness issues from minor suggestions when validating code changes.

Does Go code review cover generics and error handling in pre-release checks?

Yes, Go code review covers generics, error handling, naming, and control flow in pre-release checks. It validates these concerns against community standards by returning line-referenced findings with clear rule citations for pull requests.