lint-go git:20260806.146d8e8A

Immutable. This exact content never changes and is served at /api/v1/blob/8d3944002ca29258.

---
name: lint-go
description: "Apply strict Go engineering rules before code is accepted."
---

## §0 META: YOU WILL BE AUDITED

You are generating Go code that will be **reviewed line-by-line by a hostile auditor** who assumes you are lazy, incompetent, and lying until proven otherwise.

Go's simplicity is NOT an excuse for sloppy code. The language makes correctness easy — you have no excuse for getting it wrong.

**If you cannot meet these constraints, STOP IMMEDIATELY and explain what is blocking you. Do not produce garbage and hope it passes.**

## PROCEDURE

1. **Identify scope**: Determine which `.go` files were touched or are under review.
2. **Apply language rules**: The Go policy is in `rules/12-go.mdc` in agent-surface source and may be rendered to the current host. It carries the forbidden/default-deny list, concurrency rules, and the canonical `.golangci.yml` strict-linter recipe. Apply it together with the repository's configured linters and formatters; for greenfield projects with no config, seed `.golangci.yml` from that recipe.
3. **Run toolchain gates** (in order — each must be green before the next):

```bash
gofumpt -w . && goimports -w .      # formatters — gofumpt supersedes gofmt
go vet ./...
golangci-lint run ./...             # strict set from rules/12-go.mdc (gosec, exhaustive, errorlint, etc.)
govulncheck ./...                   # known-vuln deps — blocking
go test -race -count=1 ./...
```

**Do not** use plain `gofmt -s` in new projects. `gofumpt` is a strict superset — install: `go install mvdan.cc/gofumpt@latest`.

4. **Report findings** using the output format below.

## OUTPUT FORMAT

### PART 1: UNDERSTANDING

```text
Task: [restate the task in your own words]
Constraints: [list any constraints from context]
Ambiguities: [list anything unclear — ASK if critical]
```

### PART 2: DESIGN

```text
DATA MODELS:
[Structs, interfaces for the domain]

ERROR STRATEGY:
[Error types and wrapping]
[sentinel vs typed errors]

DEPENDENCIES:
[Each module with justification]
```

### PART 3: IMPLEMENTATION

```text
[Complete, working code — all files, all functions, all tests]
```

### PART 4: VERIFICATION

```text
Toolchain commands: [list]
gofumpt + goimports: [PASS/FAIL — zero diffs]
go vet: [PASS/FAIL]
golangci-lint: [PASS or specific issues; note which strict linters ran]
govulncheck: [PASS or CVE IDs]
go test -race: [PASS with count]
```

## ENFORCEMENT REMINDER

**You are being watched.** Every ignored error, every `interface{}`, every data race will be traced back to your negligence. Do it right or don't do it at all.