Go Code Review Skill

Systematic, read-only analysis of Go codebases and pull requests across 6 structured phases. Every phase is mandatory because small changes cause large bugs and skipping phases misses race conditions, compilation errors, and edge cases that visual inspection alone cannot catch. This skill gathers context, runs automated checks, analyzes quality, and reports findings -- it operates in read-only mode.

Available Scripts

• scripts/check-interface-compliance.sh -- Find exported interfaces missing compile-time var _ I = (*T)(nil) checks. Run bash scripts/check-interface-compliance.sh --help for options.

Instructions

Phase 1: Context Understanding

Goal: Understand what changed and why before analyzing code.

Step 1: Read project conventions

Read the repository CLAUDE.md first because project conventions override default review expectations. Note any project-specific linting rules, naming conventions, or architectural decisions that should inform the review.

Step 2: Review scope analysis