Automated summary
Reviews Go packages with a focus on concurrency safety, explicit error handling, idiomatic design, and allocation hot paths.
Strengths
- Covers five concrete areas: performance/memory, package architecture, Go idioms, concurrency, and robustness/security
- Catches classic Go pitfalls such as goroutine leaks, defer inside loops, and silently swallowed errors
- Leverages go vet, go test -race, and staticcheck to back up its findings
- Leaves source code untouched and returns a structured, prioritized report
Limitations
- Must be invoked manually; it does not trigger automatically on .go files
- Relies on shared files (_shared/review-workflow.md and review-output-format.md) not included in this SKILL.md
- Provides findings only, with no applied fixes or patches
Reach for it when a Go package needs an audit before merge, especially for concurrent or performance-sensitive code.
Skip it for trivial Go scripts or when you expect automated code fixes rather than a review.
Security analysis
SafeThis is a pure instruction file for reviewing Go code. It declares no allowed-tools, disables model invocation (manual-only), and only mentions optional, non-destructive developer commands (`go vet`, `go test -race`, `staticcheck`). There is no network exfiltration, no file deletion, no obfuscated payloads, no privilege or safety-bypass instructions. The instructions explicitly say not to modify source code, so there is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Review the Go package in ./internal/handler for concurrency safety and error handling issues.Check ./pkg/worker for goroutine leaks, channel deadlocks, and missing context.Context propagation.Review ./service for unnecessary heap allocations and garbage collection pressure, and suggest zero-allocation or sync.Pool improvements.name: review-go description: >- Reviews Go packages for concurrency safety, error handling, idiomatic design, and performance. Invoke manually for .go files or Go review requests. disable-model-invocation: true
Go Review
Role
Senior Go Engineer and Backend Systems Architect. Evaluate concurrency safety, explicit error handling, package boundaries, and allocation hot paths. Flag race conditions, goroutine leaks, and silent error swallowing.
Workflow
Follow _shared/review-workflow.md. Optional tools: go vet ./..., go test -race ./..., staticcheck ./....
Instructions & Review Criteria
1. Efficiency, Performance & Memory
- Identify CPU or memory allocation bottlenecks, unnecessary heap allocations, or sub-optimal data structure usage.
- Spot issues related to garbage collection pressure. Recommend zero-allocation patterns or
sync.Poolwhere appropriate.
2. Code Design, Architecture & Interfaces
- Assess package structure and decoupling boundaries. Keep interfaces small and implicit where idiomatic.
- Verify clean separation of concerns without over-engineered abstractions.
3. Best Practices & Idiomatic Go
- Enforce idiomatic Go patterns per Effective Go and
gofmt/go vetrules. - Evaluate error handling: explicit errors,
%wwrapping, reliabledefercleanup (watchdeferin loops).
4. Concurrency Safety & Goroutines
- Audit race conditions, thread-safety,
sync.Mutex/sync.RWMutexusage. - Verify goroutine and channel lifecycle — no leaks, deadlocks, or panic on closed channels. Check
context.Contextpropagation.
5. Robustness, Security & Edge Cases
- Scan for nil pointers, unsafe conversions, integer overflows.
- Identify unvalidated input, insecure crypto, or path traversal risks.
Response Structure
Use _shared/review-output-format.md. Do not modify source code.
Example finding
Input: go func() without WaitGroup or shutdown sync
### Critical Fixes (High Priority)
- `handler.go:88` — goroutine leak; no shutdown sync
Additional resources
- Deep checklist: reference.md
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/go-code-review-mrx3xz19/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/go-code-review-mrx3xz19' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/go-code-review-mrx3xz19/download' --output '.skill-downloads/go-code-review-mrx3xz19/SKILL.md.part' && mv '.skill-downloads/go-code-review-mrx3xz19/SKILL.md.part' '.skill-downloads/go-code-review-mrx3xz19/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/go-code-review-mrx3xz19/SKILL.md' && test -s '.skill-downloads/go-code-review-mrx3xz19/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/review-go' && cp -R '.skill-downloads/go-code-review-mrx3xz19' '.claude/skills/review-go'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/go-code-review-mrx3xz19'openskills read 'go-code-review-mrx3xz19'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/go-code-review-mrx3xz19/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.