3 description: Format, lint, test, and build. Use before every commit.
8 Run every command in the Nix development shell. Use
9 `nix develop -c COMMAND` when direnv does not load the shell.
13 1. Format all files with `bin/format`.
14 2. Run the checks with `bin/check`. Its golangci-lint config keeps the
15 standard linters and adds `errorlint`, `gocritic`, `testifylint`,
16 `revive`, `wrapcheck`, `nlreturn`, and `wsl_v5`. The settings in
17 `.golangci.yml` match the Go rules.
18 3. Run `git add` on new files, then run `nix build` and
20 4. Fix every failure and run the steps again. Do not disable a linter or
21 add a `nolint` directive to get a pass, unless the user agrees.
22 5. Review the final diff against the rules. Passing tools do not replace
24 - Read `AGENTS.md` and the `SKILL.md` of each skill of the task again
25 from disk now. Do not work from memory of an earlier read.
26 - Go through the diff one rule at a time, and for each rule look at
27 every changed line that it covers. For Go code, check each section
28 of `go-code`, also for the tests.
29 - Fix each finding, then run steps 1 to 4 again.
31 Tell the user about each check that cannot run and each failure that