go-linting
Use when setting up linting, configuring golangci-lint, or fixing linter warnings in Go projects. Provides recommended linter sets, golangci-lint configuration, CI integration, and Makefile targets.
What this skill does
# Go Linting
Recommended linters and configuration for Go projects.
## golangci-lint Setup
golangci-lint is the standard linter aggregator for Go. Install it as a tool dependency in your module:
```bash
# Add to go.mod (Go 1.24+)
go get -tool github.com/golangci/golangci-lint/cmd/golangci-lint
# Or install directly
go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
```
## Recommended Configuration
Place `.golangci.yml` at the project root. This uses the golangci-lint v2 config format:
```yaml
version: "2"
run:
timeout: 5m
go: "1.25"
linters:
enable:
- errcheck # unchecked errors
- govet # go vet checks
- staticcheck # comprehensive static analysis (includes gosimple)
- revive # flexible linter, replaces golint
- ineffassign # unused assignments
- unused # unused code
- misspell # spelling in comments and strings
- unconvert # unnecessary type conversions
- gocritic # opinionated style and performance checks
- errname # error naming conventions (Err prefix)
- errorlint # error wrapping patterns
- copyloopvar # loop variable copy issues (pre-Go 1.22)
- nilerr # returning nil when err is not nil
- bodyclose # unclosed HTTP response bodies
- prealloc # slice preallocation
settings:
revive:
rules:
- name: exported
arguments:
- "checkPrivateReceivers"
- name: blank-imports
- name: context-as-argument
- name: context-keys-type
- name: error-return
- name: error-strings
- name: error-naming
- name: increment-decrement
- name: var-naming
- name: package-comments
- name: range
- name: receiver-naming
- name: indent-error-flow
- name: empty-block
- name: superfluous-else
- name: unreachable-code
- name: redefines-builtin-id
gocritic:
enabled-tags:
- diagnostic
- style
- performance
errcheck:
check-type-assertions: true
check-blank: true
govet:
enable-all: true
exclusions:
rules:
# Allow unused parameters in interface implementations
- linters:
- revive
text: "unused-parameter"
# Test files can use dot imports
- path: _test\.go
linters:
- revive
text: "dot-imports"
formatters:
enable:
- goimports # import formatting and grouping
settings:
goimports:
local-prefixes:
- yourcompany.com
issues:
max-issues-per-linter: 0
max-same-issues: 0
```
Update `local-prefixes` under `formatters.settings.goimports` to match your module path.
Note: this config uses golangci-lint v2 format (`version: "2"`). If you are on golangci-lint v1, run `golangci-lint migrate` to convert, or remove the `version` line and move `formatters` back into `linters`.
## Makefile Integration
```makefile
.PHONY: lint lint-fix
lint: ## Run linters
go tool golangci-lint run ./...
lint-fix: ## Run linters with auto-fix
go tool golangci-lint run --fix ./...
```
If golangci-lint is not a tool dependency:
```makefile
lint:
golangci-lint run ./...
```
## CI Integration
### GitHub Actions
```yaml
name: lint
on: [push, pull_request]
jobs:
golangci-lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: "1.25"
- uses: golangci/golangci-lint-action@v6
with:
version: latest
```
## Per-Linter Guidance
### errcheck
Finds unchecked errors. Fix by handling or explicitly ignoring:
```go
// Wrong: error ignored silently
json.Unmarshal(data, &v)
// Correct: handle the error
if err := json.Unmarshal(data, &v); err != nil {
return fmt.Errorf("unmarshal config: %w", err)
}
```
### errorlint
Enforces proper error wrapping and comparison:
```go
// errorlint flags this: use errors.Is instead
if err == ErrNotFound { }
// Correct
if errors.Is(err, ErrNotFound) { }
```
### bodyclose
Catches unclosed HTTP response bodies:
```go
resp, err := http.Get(url)
if err != nil {
return err
}
defer resp.Body.Close() // bodyclose checks for this
```
### govet
Runs the same checks as `go vet` plus additional analyzers. Key checks:
- **printf**: format string / argument mismatch
- **shadow**: variable shadowing
- **structtag**: malformed struct tags
- **copylocks**: passing locks by value
## Suppressing False Positives
```go
//nolint:errcheck // intentionally ignoring close error on read-only file
_ = f.Close()
//nolint:gocritic // hugeParam: passing by value is intentional here
func process(cfg Config) { }
```
Use `//nolint` comments sparingly. Prefer fixing the issue over suppressing it.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.