go-makefile-writer

Generate Go root Makefiles with build, test, lint, and run targets.

29|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/johnqtcg/awesome-skills --skill go-makefile-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-makefile-writer
Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/go-makefile-writer
Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill go-makefile-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rg, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Canonicalize and streamline the creation or refactor of a robust root Makefile that unifies build, test, lint, and run targets for Go projects, delivering self-documenting helpers, predictable artifacts, and maintainable target naming across repositories.

Core Features & Use Cases

  • Generates or refactors a root Makefile that consolidates build, test, lint, and run targets for Go projects.
  • Injects version information into binaries, supports per-entrypoint targets, and handles monorepo layouts with module-aware planning.
  • Ensures explicit .PHONY declarations, Go version awareness, and compatibility with common CI workflows.

Quick Start

Install the skill and run the workflow to generate a deterministic root Makefile for your Go project.

Frequently Asked Questions about go-makefile-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize root Makefiles for Go projects across multiple repositories?

Standardize root Makefiles for Go projects by automating the configuration of build, test, lint, and run targets to ensure predictable artifacts and maintainable target naming across repositories. This generates a deterministic, reviewable output.

Can I use a root Makefile to handle monorepo layouts with multiple Go entrypoints?

Handle monorepo layouts with a root Makefile by using module-aware planning that supports per-entrypoint builds. This ensures compatibility with common CI workflows while maintaining explicit .PHONY declarations.

What is the best way to add cross-compilation and Docker support to a Go Makefile?

Add cross-compilation and Docker support to a Go Makefile through optional build configurations included during generation. This approach enforces Go version awareness and safety checks alongside standard build targets.

Do I need any specific tools installed to generate a Go Makefile with version injection?

Generate a Go Makefile with version injection requires having the ripgrep tool installed as a dependency. The skill uses ripgrep to perform safety checks and gather module-aware planning information for the project.