go-review

Name: go-review
Availability: InStock
Author: vmkteam

Review the current git diff of Go code with six expert personas.

6|Updated Apr 5, 2026

Search Tags:#go #code-review #development-process #peer-review #git-diff #multi-persona #go-community

Ready to run

npx skills add https://github.com/vmkteam/claude-plugins --skill go-review-vmkteam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-review
Source: https://github.com/vmkteam/claude-plugins/tree/main/plugins/developer/skills/go-review
Command: npx skills add https://github.com/vmkteam/claude-plugins --skill go-review-vmkteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conduct multi-persona reviews of the current git diff for Go code to catch issues from multiple expert perspectives before committing.

Core Features & Use Cases

Multi-persona assessment by Cheney, Pike, Valsorda, Hashimoto, Bourgon and common reviewer.
Enforces diff-only review, skipping generated files, with per-issue severity tagging.
Provides structured feedback with file:line references and a log of findings for decision making.

Quick Start

Instruct the system to perform a Go code review on the current diff by invoking the go-review workflow and supply the changes for evaluation.

Frequently Asked Questions about go-review

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

FAQPage Schema

How do I perform a Go code review on my current git diff?▼

To perform a Go code review on your current git diff, invoke the go-review workflow and supply the changes for evaluation. The system will analyze the diff using six expert personas and provide structured feedback with file:line references and severity tags.

What is multi-persona code review and how does it work for Go?▼

Multi-persona code review for Go assesses git diffs from six named expert perspectives, including Cheney, Pike, and Valsorda. It aggregates feedback from these distinct viewpoints to catch issues before committing, providing per-issue severity tags and file:line references.

Does the Go code review process skip generated files?▼

Yes, the Go code review process enforces diff-only reviews and automatically skips generated files. This ensures the multi-persona assessment focuses solely on manually written code changes, providing structured feedback with severity tags and file:line references.

When should I run a peer review on my Go code changes?▼

You should run a peer review on your Go code changes after implementing a task and before committing, or when explicitly requested via 'code review'. This multi-persona assessment catches issues from six expert perspectives before they enter your commit history.

Can I get severity-tagged feedback from multiple Go expert perspectives?▼

Yes, you can get severity-tagged feedback from multiple Go expert perspectives including Cheney, Pike, Valsorda, Hashimoto, Bourgon, and a common reviewer. The system documents per-issue severity and provides a log of findings with file:line references for decision making.