review-golang

Review git-changed Go files for idiomatic issues and library usage.

11|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/ivklgn/ai --skill review-golang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-golang
Source: https://github.com/ivklgn/ai/tree/main/claude/skills/review-golang
Command: npx skills add https://github.com/ivklgn/ai --skill review-golang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go projects frequently undergo changes that require careful review to catch idiomatic issues, error handling gaps, and library usage problems. This skill automates a thorough examination of all git-changed .go files to improve code quality, consistency, and maintainability.

Core Features & Use Cases

  • Identify changed Go files from the current branch or staged changes, excluding primary test files, to focus reviews on real code changes.
  • Pre-fetch relevant library documentation for non-standard dependencies using Context7 MCP to inform the review with accurate usage guidance.
  • Launch golang-pro guided review with a structured prompt that assesses idioms, error handling, memory patterns, and library usage.
  • Apply findings to CI or pre-merge workflows to improve code quality, reliability, and maintainability on Go projects.

Quick Start

Provide the changed Go files to review and let the skill perform a comprehensive analysis using golang-pro and Context7 documentation.

Frequently Asked Questions about review-golang

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

FAQPage Schema
How do I review changed Go files for code quality and idioms?

Reviewing changed Go files for code quality involves analyzing git diffs of .go files to assess idioms, error handling, and memory patterns. This skill automates that examination to improve consistency and maintainability in Go projects.

Can I use Context7 documentation to check non-standard library usage in Go code?

Yes, you can verify non-standard library usage in Go code by pre-fetching relevant documentation with Context7 MCP. This informs the review process with accurate usage guidance to ensure dependencies align with current docs.

What is the best way to automate static analysis for Go pull requests?

Automating static analysis for Go pull requests is best achieved by identifying changed .go files and applying golang-pro review guidelines. This structured approach assesses code quality, reliability, and library usage before merging.

Does this Go code review process include primary test files?

No, this Go code review process explicitly excludes primary test files to focus reviews on real code changes. It targets git-changed .go files to ensure the core logic maintains quality and consistency.

How do I apply golang-pro review guidelines to staged Go changes?

You apply golang-pro review guidelines to staged Go changes by launching a guided review with a structured prompt. This assesses idioms, error handling, memory patterns, and library usage across the identified changed files.