Skip to content
cccskills
FreePublished on GitHub

makefile-development-workflow

Standardizes Makefile-based build and test workflows with reproducible targets. Use when creating or refining helpful build, test, and clean targets.

The English summary is being prepared. Showing the original description.

Works withDocker
See how to install

Files included (2)

  • SKILL.md3.8 KB
  • references/anatomy.md17.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Makefile Development Workflow

A minimal, well-structured Makefile for any project:

.PHONY: help build test clean

.DEFAULT_GOAL := help

help: ## Show this help message
	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / { printf "  \033[36m%-15s\033[0m %s\n", $$1, $$2 }' $(MAKEFILE_LIST)

build: ## Build the project
	@echo "Building..."
	# Add your build command here

test: ## Run tests
	@echo "Running tests..."
	# Add your test command here

clean: ## Clean build artifacts
	@echo "Cleaning..."
	rm -rf build/ dist/ __pycache__/

Run make help to see all available commands.


Best Practices

1. Always Use .PHONY

.PHONY: help build test clean install

Prevents conflicts with files of the same name and ensures targets always run.

2. Use .DEFAULT_GOAL

.DEFAULT_GOAL := help

Makes make show help by default instead of the first target.

3. Document Targets with ## Comments

build: ## Build the project (required)
	@echo "Building..."

test: ## Run tests (required)
	@echo "Testing..."

The ## comment after the target is picked up by auto-generated help.

4. Use ?= for Overridable Variables

PYTHON   ?= python3   # Can be overridden: make PYTHON=python3.11 test
VENV     ?= .venv     # Can be overridden: make VENV=myenv test

5. Use SHELL := /bin/bash

SHELL := /bin/bash

Ensures bash features (like command -v) work consistently.

6. Use @ to Suppress Command Echo

build:
	@echo "Building..."  # @ suppresses "echo Building..."
	@cd server && go build -o bin/server ./cmd/server

7. Use $$ for Shell Variables in Make

check-env:
	@if [ -z "$$API_KEY" ]; then echo "WARNING: API_KEY not set"; fi

$$ becomes $ in the shell.

8. Use || true to Prevent Failures

clean:
	@pkill -f "uvicorn" || true   # Don't fail if process isn't running
	@rm -rf build/ || true        # Don't fail if directory doesn't exist

9. Use Multi-Line Commands with \

test:
	@if [ "$(VERBOSE)" = "1" ]; then \
		pytest tests/ -v -s; \
	else \
		pytest tests/; \
	fi

10. Use && for Chained Commands

install:
	pip install -e ".[dev]" && echo "[OK] Installed"

Quick Command Cheat Sheet

CommandPurpose
make helpShow all available commands
make buildBuild the project
make testRun tests
make cleanClean build artifacts
make installInstall dependencies
make lintRun linter
make formatFormat code
make devStart development mode
make allRun full pipeline
make docker-upStart Docker services
make docker-downStop Docker services
make -j4Run with 4 parallel jobs
make VAR=value targetOverride variable for target

Language-Specific Templates & Patterns

For detailed language-specific Makefiles, patterns, and advanced configurations, see references/anatomy.md.

Quick links:

  • Python projects: templates, pytest setup, venv targets
  • Go projects: build, testing, hot reload patterns
  • Node.js / TypeScript: npm integration, test runners
  • R packages: devtools targets, documentation
  • Docker integration: compose management, build patterns
  • Multi-phase pipelines: setup -> build -> test -> report
  • Conditional tool detection: graceful fallbacks
  • Variable overrides, pattern rules, parallel execution

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Distills enduring architectural decisions and design rationale from wave orchestration plans or historical git changes into structured, tracked Architecture Decision Records (ADRs). Use pre-wave to resolve active architectural constraints or post-wave to record enduring decisions in docs/decisions/.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

Create and maintain AGENTS.md files for project onboarding and grounding. Use when initialized in a new project, when project structure changes significantly, or when creating subfolder-level AGENTS.md files for complex monorepos.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

Audit and update an arbitrary codebase to follow the Code.mil federal open-source licensing model (MIT with 17 U.S.C. Section 105 disclaimers and INTENT.md), including CRAN/R package DESCRIPTION setup.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes - Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

Reads Copilot conversation history and extracts executive-ready success stories. Use when the user asks to study prior Copilot sessions, summarize what was done before, mine evidence, or quantify time, cost, risk, and priority alignment from GitHub Copilot history in any workspace or repository.

The English summary is being prepared. Showing the original description.

AndrewBrown-USDA/aigb-skills-usda7Updated Oct 16, 2026

See all skills by AndrewBrown-USDA

Report a problem with this skill