golang-patterns

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

Quality

43%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/golang-patterns/SKILL.md

Evaluation results

100%

10%

Multi-Source Configuration Loader

Error handling patterns

Criteria

Without context

With context

fmt.Errorf %w wrapping

100%

Context in error messages

100%

Custom error type

100%

Sentinel error variables

100%

errors.Is or errors.As usage

100%

No ignored errors

100%

No panic for control flow

100%

Early return pattern

100%

Errors returned not swallowed

100%

No naked returns

100%

90%

30%

Concurrent Health Check Tool

Concurrency and context patterns

Criteria

Without context

With context

errgroup usage

100%

errgroup.WithContext called

100%

context.WithTimeout + defer cancel

100%

Context-aware HTTP requests

100%

Goroutine leak prevention

100%

Context as first parameter

100%

No ignored errors

100%

70%

Error wrapping

100%

Race-safe result collection

100%

g.Wait() error handled

30%

86%

31%

High-Throughput Log Record Processor

Package design and performance patterns

Criteria

Without context

With context

Functional options pattern

16%

100%

Accept interfaces, return concrete

20%

60%

Standard project layout

50%

Package naming conventions

100%

No package-level mutable state

70%

90%

Pre-allocated slices

70%

100%

strings.Builder for assembly

100%

sync.Pool for buffer reuse

16%

100%

Small focused interfaces

80%

100%

Interfaces at use site

50%

Repository: haniakrim21/everything-claude-code
Commit: ae2cadd

Evaluated: 18 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Multi-Source Configuration Loader Concurrent Health Check Tool High-Throughput Log Record Processor

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.