Go developers finally have a native solution for documentation linting frustrations. A new tool called gomarklint addresses the common pain points of context switching and slow CI pipelines. Its creator built it after getting tired of installing Node.js or Ruby just to run a Markdown linter in a Go environment.

Speed is the primary selling point. The tool leverages Go's concurrency to check 180 files containing over 100,000 lines of text in under 50 milliseconds. This near-instant feedback loop allows developers to catch issues immediately rather than waiting on lengthy CI checks.

Beyond raw speed, gomarklint enforces critical documentation standards out of the box. It detects broken links, enforces proper heading hierarchies, and flags duplicate headings that break anchor links. While it works with zero configuration, users can customize rules via a simple JSON file.

The roadmap includes accessibility improvements like image alt-text validation and auto-fixing capabilities. It is available now on GitHub.