dev.go-project

Standardize Go build, test, and lint commands by routing tasks through the project's Makefile. The skill reads and interprets Makefile rules to execute targets, enforcing consistent workflows and adhering to project-specific tool versions and conventions.

A Makefile-first workflow for Go development centralizes common tasks like building, testing, linting, and formatting behind Makefile targets. Instead of invoking Go tools directly, the workflow discovers and executes make targets defined by the project to prevent command drift and inconsistency.

Yes, your Go project needs a Makefile in the repository root to fully automate formatting and testing. The workflow discovers available targets by reading the root Makefile, applying actions through prescribed project conventions rather than direct tool invocations.

If a Makefile target isn't defined for a Go task, the workflow provides safe fallbacks. It suggests or falls back to direct commands with guidance, ensuring the development task can still proceed even when the Makefile lacks specific build, test, lint, or format rules.

Use Makefile targets instead of direct Go tool invocations to eliminate ad-hoc commands that create drift and inconsistency. Centralizing development tasks behind the Makefile ensures teams follow the project's prescribed workflow, tool versions, and conventions for reliable results.