go-development

分类: 运维与交付 | 上传者: netresearch | 下载: 0 | 版本: v1.0（最新）

Use when developing Go applications, implementing job schedulers, Docker integrations, LDAP clients, or building resilient services with thorough testing and performance optimization.

更新日志: Source: GitHub https://github.com/netresearch/go-development-skill

目录结构

当前层级: skills/go-development/

📁 references/
- 📄 api-design.md 9.7 KB
- 📄 architecture.md 12.0 KB
- 📄 cron-scheduling.md 9.3 KB
- 📄 docker.md 11.1 KB
- 📄 fuzz-testing.md 4.0 KB
- 📄 ldap.md 15.3 KB
- 📄 linting.md 9.2 KB
- 📄 logging.md 9.9 KB
- 📄 makefile.md 4.6 KB
- 📄 modernization.md 7.1 KB
- 📄 mutation-testing.md 4.8 KB
- 📄 resilience.md 11.3 KB
- 📄 testing.md 27.6 KB
📁 scripts/
- 📄 verify-go-project.sh 2.3 KB
📄 SKILL.md 3.9 KB

SKILL.md

---
name: go-development
description: "Use when developing Go applications, implementing job schedulers, Docker integrations, LDAP clients, or building resilient services with thorough testing and performance optimization."
---

# Go Development Patterns

## When to Use

- Building Go services or CLI applications
- Implementing job scheduling or task orchestration
- Integrating with Docker API
- Building LDAP/Active Directory clients
- Designing resilient systems with retry logic
- Setting up comprehensive test suites

## Required Workflow

**For comprehensive reviews, ALWAYS invoke these related skills:**

1. **Security audit** - Invoke `/netresearch-skills-bundle:security-audit` for OWASP analysis, vulnerability assessment, and security patterns
2. **Enterprise readiness** - Invoke `/netresearch-skills-bundle:enterprise-readiness` for OpenSSF Scorecard, SLSA compliance, supply chain security
3. **GitHub project setup** - Invoke `/netresearch-skills-bundle:github-project` for branch protection, rulesets, CI workflow validation

A Go development review is NOT complete until all related skills have been executed.

## Core Principles

### Type Safety

- **Avoid:** `interface{}` (use `any`), `sync.Map`, scattered type assertions, reflection, `errors.As` with pre-declared variables
- **Prefer:** Generics `[T any]`, `errors.AsType[T]` (Go 1.26), concrete types, compile-time verification
- **Modernize:** Run `go fix ./...` after Go upgrades to apply automated modernizers

### Consistency

- One pattern per problem domain
- Match existing codebase patterns
- Refactor holistically or not at all

### Conventions

- Errors: lowercase, no punctuation (`errors.New("invalid input")`)
- Naming: ID, URL, HTTP (not Id, Url, Http)
- Error wrapping: `fmt.Errorf("failed to process: %w", err)`

## References

Load these as needed for detailed patterns and examples:

| Reference | Purpose |
|-----------|---------|
| `references/architecture.md` | Package structure, config management, middleware chains |
| `references/logging.md` | Structured logging with log/slog, migration from logrus |
| `references/cron-scheduling.md` | go-cron patterns: named jobs, runtime updates, context, resilience |
| `references/resilience.md` | Retry logic, graceful shutdown, context propagation |
| `references/docker.md` | Docker client patterns, buffer pooling |
| `references/ldap.md` | LDAP/Active Directory integration |
| `references/testing.md` | Test strategies, build tags, table-driven tests |
| `references/linting.md` | golangci-lint v2, staticcheck, code quality |
| `references/api-design.md` | Bitmask options, functional options, builders |
| `references/fuzz-testing.md` | Go fuzzing patterns, security seeds |
| `references/mutation-testing.md` | Gremlins configuration, test quality measurement |
| `references/makefile.md` | Standard Makefile interface for CI/CD |
| `references/modernization.md` | Go 1.26 modernizers, `go fix`, `errors.AsType[T]`, `wg.Go()` |

## Quality Gates

Run these checks before completing any review:

```bash
golangci-lint run --timeout 5m    # Linting
go vet ./...                       # Static analysis
staticcheck ./...                  # Additional checks
govulncheck ./...                  # Vulnerability scan
go test -race ./...                # Race detection
```

## Go Stdlib Vulnerability Fixes

When `govulncheck` reports stdlib vulnerabilities (e.g., `GO-2026-xxxx` in `crypto/x509`, `net/url`, `os`, `html/template`):

1. Check fix version: `curl -sL "https://vuln.go.dev/ID/GO-2026-XXXX.json" | jq '.affected[0].ranges[0].events[] | select(.fixed) | .fixed'`
2. Update `go.mod`: change `go X.Y.Z` to the fixed version
3. Run `go mod tidy` to verify no `go.sum` changes needed
4. CI workflows using `go-version-file: go.mod` will automatically pick up the new version

**Important:** For repos with branch protection/merge queues, create a PR branch — don't push directly to main.

---

> **Contributing:** Submit improvements to https://github.com/netresearch/go-development-skill

登录后下载/点赞/收藏 ❤ 5 | ★ 0

go-development

目录结构

SKILL.md

举报内容

提示