
Go Code Review
This is a structured Go code reviewer that enforces a four-step workflow: check go.mod for the version baseline, read full function context (not just diffs), scope the relevant checklist blocks, then run verification protocol before reporting anything. It covers the usual suspects like error handling and goroutine leaks, but also includes version-gated advice for Go 1.18+ generics, 1.21+ slog, and 1.22 loop semantics. The severity calibration is sensible, goroutine leaks and race conditions block merge while missing doc comments are minor. What I appreciate is the explicit "Valid Patterns" section that tells it not to flag intentional underscore assignments or functional options, which cuts down on false positives. Use this when you want methodical Go reviews that respect idiomatic code instead of blindly applying rules.
- skills.sh installs
- 204
- GitHub stars
- 87
- last updated
- Aug 21, 2026
Install
$ npx -y skills add existential-birds/beagle --skill go-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Files
Go Code Review
Review Workflow
Follow this sequence in order. Do not emit findings until every Pass below is satisfied.
-
Baseline
go.mod— Opengo.modand read thegodirective.
Pass: You can state the exactgo X.YYvalue (in the review preamble or working notes). Apply version-gated advice only when it matches this baseline (loop capture pre-1.22,slog/structured logging from 1.21,errors.Joinfrom 1.20). -
Read surrounding code — For each changed
.gofile, read full functions or logical units that contain the edits, not only the diff hunk.
Pass: At least one full enclosing function (or package-levelinit/var block) containing the change was read per changed file. -
Scope the checklist — Decide which Review Checklist blocks apply (error handling, concurrency, interfaces/types, resources, naming). Load references for those blocks; skip blocks that are irrelevant to the diff.
Pass: The review (or working notes) lists which checklist blocks you applied, or marks blocks N/A with a one-line reason tied to the diff (e.g. “no concurrency in change”).
Sponsors
Details
- Repository
- github.com/existential-birds/beagle
- Categories
- Git & Pull Requests, Code Review & Quality, Debugging, Go, Design & UI/UX
- First seen
- Jun 3, 2026
More from existential-birds/beagle
All 40- Shadcn Code Review204
- Swift Testing Code Review194
- Sqlite Vec171
- Pydantic Ai Tool System161
- Deepagents Architecture160
- Langgraph Implementation160
- Pydantic Ai Testing146
- Pydantic Ai Dependency Injection141
- Deepagents Implementation140
- Deepagents Code Review132
- Github Projects120
- Pydantic Ai Model Integration120
- React Flow1.3K
- Python Code Review928
- Langgraph Code Review887
- Tailwind V4817
- React Flow Advanced643
- React Router V7577
- React Flow Architecture536
- Vitest Testing471
- Docling431
- Fastapi Code Review387
- React Flow Implementation374
- Shadcn Ui356