{"enrichment":{"faq":[{"a":"go-code-review systematically audits Go source files against idiomatic patterns, error handling practices, concurrency safety, and common pitfalls. The skill applies version-aware guidance based on your project's Go baseline, covering generics, structured logging, and loop variable semantics.","q":"What does go-code-review check Go code for?"},{"a":"go-code-review includes targeted detection for goroutine leaks and concurrency safety issues. It analyzes goroutine spawning patterns, channel usage, synchronization primitives, and lifecycle management to identify potential race conditions and resource leaks in concurrent code.","q":"How does go-code-review detect goroutine safety issues?"},{"a":"Yes. go-code-review checks error handling and wrapping in Go files with high priority, examining error propagation patterns, proper use of error wrapping with fmt.Errorf, and adherence to Go error handling idioms throughout your codebase.","q":"Can go-code-review review go error handling best practices?"},{"a":"go-code-review validates Go version-specific features and semantics, including Go 1.22 loop variable changes, generics syntax, and structured logging with slog. It applies version-aware guidance tailored to your project's Go baseline.","q":"Does go-code-review handle Go version-specific features?"},{"a":"go-code-review ensures proper resource cleanup and lifecycle management by reviewing defer statements, file handle closures, connection pooling, and context propagation. It detects missing cleanup calls and improper resource lifecycle patterns.","q":"What resource cleanup issues can go-code-review identify?"},{"a":"go-code-review follows a structured workflow that reads full context, applies targeted checklists, and verifies findings before reporting issues with severity calibration. This systematic approach ensures accurate, actionable feedback on code quality and safety.","q":"How does go-code-review report its findings?"}],"shadow_tags":["static-analysis","best-practices","concurrency-safety","resource-management","error-patterns","code-quality","golang-idioms","version-aware"],"summary_rewrite":"Go Code Review systematically audits Go source files against idiomatic patterns, error handling practices, concurrency safety, and common pitfalls. The skill applies version-aware guidance based on your project's Go baseline, covering generics, structured logging, and loop variable semantics. It follows a structured workflow that reads full context, applies targeted checklists, and verifies findings before reporting issues with severity calibration."},"files":[{"bytes":7769,"path":"plugins/beagle-go/skills/go-code-review/SKILL.md","sha256":"3e54eb36ccb6b7dd34dcf2fa9f718ba49bdb89a82c01b24121d747fa2938aaa3","url":"https://skillfed.io/files/existential-birds/beagle/go-code-review/79aed1bc/SKILL.md"}],"id":"existential-birds/beagle/go-code-review","links":{"html":"https://skillfed.io/existential-birds/beagle/go-code-review","md":"https://skillfed.io/existential-birds/beagle/go-code-review.md","repo":"https://github.com/existential-birds/beagle"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":10,"language":"TypeScript","last_updated":"2026-07-21","license":"Apache-2.0","name":"go-code-review","publisher":"existential-birds","stars":74},"relations":{"similar":[{"id":"pedronauck/skills/golang-pro"},{"id":"devantler-tech/ksail/golang-pro"},{"id":"Jeffallan/claude-skills/golang-pro"},{"id":"existential-birds/beagle/go-testing-code-review"},{"id":"smallnest/goal-workflow/modern-go"},{"id":"saisudhir14/claude-skills/claude-skills"},{"id":"samber/cc-skills-golang/golang-modernize"},{"id":"existential-birds/beagle/swift-code-review"},{"id":"JetBrains/go-modern-guidelines/use-modern-go"},{"id":"personamanagmentlayer/pcl/go-expert"}]},"slug":{"owner":"existential-birds","repo":"beagle","skill":"go-code-review"},"version":"79aed1bc"}