go-spec-reviewer

To review a Go design specification for completeness, you can submit your pre-build design doc to validate requirements, check for contradictions, and ensure the spec is ready for idiomatic implementation.

Idiomatic Go design validation evaluates your specification through a Go-first lens, verifying simplicity, small interfaces, explicit errors, context use, concurrency choices, and package design before development starts.

Yes, you can validate Cobra and Viper conventions in a CLI tool design doc. The review applies specific checks for command registration and flag design when the specification touches command-line tools.

Yes, Go spec review explicitly checks context propagation and concurrency choices. It evaluates these architectural elements against idiomatic Go practices to ensure your design is safe and practical to build.

You need a pre-implementation review for a Go service when you want to catch missing requirements and architectural flaws early. It provides a fast verdict on whether your design doc is ready to turn into code.

Automated Go spec review focuses on architectural readiness and idiomatic practices like package boundaries and error handling, but cannot verify business logic correctness or replace actual code execution testing.