makefile-script-developer

Write production-ready GNU Makefiles with strict shell mode (`SHELL := /bin/bash` + `.SHELLFLAGS := -euo pipefail -c`), validated multi-environment configuration via `$(filter ...)`, pre-flight check targets (`check-tools`, `check-env`), structured logging with timestamps, confirmation gates for destructive ops, layered `.env` includes, platform detection, and self-documenting help. Use this skill whenever the user asks to write a Makefile, harden an existing one, add a target, build a deploy/release pipeline, automate Terraform/Helm/Kubernetes/Docker/build workflows, or expose tasks as `make <target>` — including casual phrasings like "write a Makefile", "add a make target", "automate this in make", "give me a build pipeline", or "clean up the Makefile". Also use when reviewing an existing Makefile for safety, error handling, or organization issues.

Jump to install

Repository: MKAbuMattar/skills
Last source activity: July 26, 2026 at 14:07
Detected SKILL.md language: English
Stars: 1
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/MKAbuMattar/skills --skill makefile-script-developer

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

15 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

humanizer

Edit or review text to remove signs of AI-generated writing — inflated significance ('pivotal moment', 'evolving landscape'), promotional language ('nestled', 'breathtaking'), superficial -ing analyses ('highlighting', 'underscoring'), vague attributions ('industry experts'), em-dash overuse, rule-of-three patterns, AI vocabulary ('delve', 'tapestry'), copula avoidance ('serves as'), passive voice, negative parallelisms ('not just X, but Y'), filler phrases, sycophantic openings ('Great question!'), and the rest of the 29-pattern catalog from Wikipedia's 'Signs of AI writing'. Works on written prose only: essays, articles, drafts, documentation, emails, marketing copy. Use this skill whenever the user wants to humanize text, remove AI tells, edit AI-sounding writing, make text sound less like ChatGPT, do a final 'does this read like a person wrote it' pass, or hits you with phrases like 'humanize this', 'make this sound less AI', 'remove the AI slop', 'edit this draft', or 'why does this read like an LLM'.

2026-07-28

linux-script-developer

Write production-ready Bash scripts with strict error handling (`set -euo pipefail`), validated argument parsing, colored user feedback, and cross-platform compatibility (Linux, macOS, Windows via Git Bash/WSL). Use this skill whenever the user asks for a `.sh` script, a shell script, a Bash one-liner installer, a CLI wrapper, or a file-batch processor, and for server and deployment automation generally: releasing or rolling back a build, restarting or health-checking a service, scheduled and cron jobs, log rotation, backup and restore, syncing files between machines, and bootstrapping a box. Includes casual phrasings like "write a script to ...", "automate this in bash", or "make me a shell tool". Also use when reviewing or hardening an existing Bash script.

2026-07-28

teacher-mode

Explain any concept like an experienced mentor: clear, first-principles, and brief. Use this skill whenever the user wants to understand something rather than just get it fixed, including "explain", "teach me", "how does X work", "why does X", "what is X", "help me understand", "walk me through", "ELI5", "deep dive", or "I'm learning X". Conceptual questions get answered in full; on a concrete coding task it withholds the working solution and leads with hints until the learner attempts it. Do not use when the user wants the job done rather than explained.

2026-07-27

View all from this repository

Makefile Script Developer

Production-ready GNU Makefiles. Strict shell + validated env + logging + safety gates.

When to use

The user asks to write, scaffold, or harden a Makefile.

The user wants to add or refactor a make target / workflow / build pipeline.

The user wants to automate Terraform / Helm / kubectl / Docker / build / release through make.

The user wants a self-documenting help target or wants to clean one up.

A task chain ends in "and put it in a Makefile so I can run make deploy ...".

Required structure

Every Makefile you write starts from this skeleton. Do not omit SHELL := /bin/bash, the .SHELLFLAGS line, or .DEFAULT_GOAL := help. Recipes are TAB-indented, not spaces.

SHELL := /bin/bash .SHELLFLAGS := -euo pipefail -c .DEFAULT_GOAL := help .DELETE_ON_ERROR: MAKEFLAGS += --warn-undefined-variables --no-print-directory # ---- Configuration -------------------------------------------------- ALLOWED_ENVS := dev staging prod ENV ?= dev ifeq (,$(filter $(ENV),$(ALLOWED_ENVS))) $(error ENV must be one of: $(ALLOWED_ENVS)) endif TIMESTAMP := $(shell date +"%Y-%m-%d_%H-%M-%S") LOG_DIR := logs/$(ENV) # ---- Pre-flight ----------------------------------------------------- .PHONY: check-tools check-tools: @command -v terraform >/dev/null 2>&1 || { echo "terraform not installed"; exit 1; } @echo "Tools verified" # ---- Help ----------------------------------------------------------- .PHONY: help help: ## Show this help @grep -E '^[a-zA-Z_-]+:.*? awk 'BEGIN {FS = }; {printf , $$1, $$2}'