gohawk for VS Code

Shows gohawk findings in the editor: resources that are not released on every return path, contradictory lock orders, goroutines nothing waits for, and more. Each finding carries the path that proves it.

• Findings appear shortly after you stop typing, including in unsaved files.
• Hover a finding for the usual fix; use the lightbulb to step through the reported path or to see the full evidence.
• gohawk only reports. It never edits your code.

It runs beside the official Go extension and does not replace it.

Follow the path

Put the cursor on a finding, open the lightbulb menu, and pick Step through the reported path. Everything that is not part of the path is dimmed and each step is numbered. Tab and Shift+Tab move between steps; Esc exits.

How it works

The extension starts gohawk lsp, a small process that holds no analysis state. Each check runs go vet with gohawk as its tool and exits when done, so analysis memory is released between checks.

Settings

Test files (_test.go) are not analyzed.

Large projects

The first check in a project also analyzes its dependencies. On a very large project this takes a few minutes, once; the status bar shows the progress. If checks feel slow while you type, set gohawk.run to onSave.

More

Documentation for every check is at gohawk.dev. Report problems at github.com/kojah/gohawk.