// Post-edit toolchain to run after writing or modifying any `.go` file. Load whenever a task changes Go source.
| name | writing-go |
| description | Post-edit toolchain to run after writing or modifying any `.go` file. Load whenever a task changes Go source. |
After writing or editing any .go file, run these against the changed
package(s). All must pass; fix the code, do not suppress diagnostics.
gofmt -s -w <changed-files>
go vet ./<changed-pkg>/...
staticcheck ./<changed-pkg>/... # if installed
go build ./...
go test ./<changed-pkg>/...
If the repo's AGENTS.md specifies required env vars, directories to
skip, or extra checks, follow those instead.
Apply modern Go syntax guidelines based on project's Go version. Use when user ask for modern Go code guidelines.
Using the Kronk MCP service in the default agent configuration, where Kronk is wired directly into the host (OpenCode, Kilo, Pi) as an MCP server. Exposes `fuzzy_edit` (fallback for the host's exact-match edit when whitespace / line-endings cause it to miss) and `web_search` (Brave-powered). Load whenever you need web research, or when a host edit fails on exact matching.
The ONLY sanctioned path to the Kronk MCP service (`web_search`, `fuzzy_edit`) in the rote-routed config. Every command is a `rote ...` invocation in Bash. Load whenever you need web research, or when a host edit fails on exact-string matching and you need the rote-routed `fuzzy_edit` fallback.