Agent skill

Makefile Validator

by akin-ozer in akin-ozer/cc-devops-skills

Validate, lint, audit, or check Makefiles and .mk files for errors.

Apache-2.0Auto-check passedDevelopment

Install Makefile Validator

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .claude/skills/makefile-validator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .claude/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .agents/skills/makefile-validator && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .agents/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .cursor/skills/makefile-validator && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .cursor/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/akin-ozer/cc-devops-skills.git --path devops-skills-plugin/skills/makefile-validator

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .gemini/skills/makefile-validator && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .gemini/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .github/skills/makefile-validator && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .github/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install akin-ozer/cc-devops-skills makefile-validator --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/akin-ozer/cc-devops-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/devops-skills-plugin/skills/makefile-validator .opencode/skills/makefile-validator && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "makefile-validator" agent skill from https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills/makefile-validator into .opencode/skills/makefile-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "makefile-validator", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: makefile-validator
GitHub stars: 319
Token cost: ~1.8k tokens
SKILL.md length: 641 words
Files: 8 (incl. scripts)
Skills in repo: 30
Repo updated: Jul 26, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Validate, lint, audit, or check Makefiles and .mk files for errors.

Works in 5 steps: Preflight → Baseline Validation (Default Path) → Interpret Output and Exit Code → …
Tasks that involve Linting and formatting
SKILL.md covers Overview, Trigger Guidance, Deterministic Execution Model and How to Open Docs, plus 5 more sections
Runs Shell scripts from its folder; calls bash, make and rg

What it does

Makefile Validator is an agent skill from akin-ozer/cc-devops-skills. Validate, lint, audit, or check Makefiles and .mk files for errors.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts (for example `docs/bake-tool.md`, `docs/best-practices.md` and `docs/common-mistakes.md`).

It sits in Development, covering Linting and formatting. The repository describes itself as: DevOps skills for Claude Code and Codex. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Linting and formatting

Example prompts

“/makefile-validator”

Requirements

Python 3
A Bash shell

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Preflight
Baseline Validation (Default Path)
Interpret Output and Exit Code
Progressive Reference Loading
Fix + Rerun Loop

What it can do on your machine

Read from SKILL.md and the folder at commit 276af75. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
- make
- rg
- pip3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pip3, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Makefile Validator loads about 1.8k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~22
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from akin-ozer/cc-devops-skills at commit 276af75, republished under its Apache-2.0 licence (© akin-ozer). 641 words, ~1,786 tokens.

Download SKILL.mdSave it as .claude/skills/makefile-validator/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: makefile-validator
description: Validate, lint, audit, or check Makefiles and .mk files for errors.

Makefile Validator

Overview

Use this skill to validate Makefiles with a local-first, deterministic flow.

Default validator entrypoint:

bash

bash scripts/validate_makefile.sh <makefile-path>

Validation layers:

Dependency preflight (python3, pip3, make)
GNU make syntax check (make -n --dry-run) when make is available
mbake validate
mbake format --check
Custom security, best-practice, and optimization checks
Optional checkmake and unmake checks when installed

Trigger Guidance

Use this skill when the request includes Makefile quality, linting, validation, hardening, or troubleshooting.

Trigger Phrases

"Validate this Makefile"
"Lint my .mk file"
"Find issues in this build Makefile"
"Check Makefile security problems"
"Review this Makefile before CI"

Non-Trigger Examples

Creating a brand new Makefile from scratch (use makefile-generator)
Running build targets as part of delivery
General shell scripting work unrelated to Makefiles

Deterministic Execution Model

Run from this skill directory for shortest commands:

bash

cd devops-skills-plugin/skills/makefile-validator

Step 1: Preflight

Confirm target file exists and is readable.
Confirm whether file edits are allowed (writable) or only suggestions can be returned (read-only).
Prefer the default validator path first; use fallbacks only when blocked by environment constraints.

Step 2: Baseline Validation (Default Path)

bash

# From skill directory
bash scripts/validate_makefile.sh <makefile-path>

# From repository root
bash devops-skills-plugin/skills/makefile-validator/scripts/validate_makefile.sh <makefile-path>

Always record:

command executed
exit code
summary counts (Errors, Warnings, Info)
issue locations reported by tools

Step 3: Interpret Output and Exit Code

Exit code	Meaning	Expected summary line	Action
`0`	no blocking findings	`Validation PASSED`	optional improvements only
`1`	warning-only result	`Validation PASSED with warnings`	fix recommended; merge policy dependent
`2`	error result	`Validation FAILED - errors must be fixed`	fix required, then rerun

Step 4: Progressive Reference Loading

Open only the docs required by the current findings.

Finding type	Reference doc
`.PHONY`, `.DELETE_ON_ERROR`, `.ONESHELL`, variable usage, performance structure	`docs/best-practices.md`
tabs vs spaces, dependency mistakes, credential patterns, anti-patterns	`docs/common-mistakes.md`
`mbake` behavior, formatter flags, known `mbake` caveats	`docs/bake-tool.md`

Step 5: Fix + Rerun Loop

After applying fixes, rerun:

bash

bash scripts/validate_makefile.sh <makefile-path>

Loop rules:

Stop only when no new errors are introduced.
If warnings remain intentionally, document why they are accepted.
Always report the latest rerun exit code.

How to Open Docs

Use explicit file-open commands so paths are unambiguous.

From repository root:

bash

sed -n '1,220p' devops-skills-plugin/skills/makefile-validator/docs/best-practices.md
sed -n '1,220p' devops-skills-plugin/skills/makefile-validator/docs/common-mistakes.md
sed -n '1,220p' devops-skills-plugin/skills/makefile-validator/docs/bake-tool.md
rg -n "PHONY|DELETE_ON_ERROR|ONESHELL|tab|credential|mbake" devops-skills-plugin/skills/makefile-validator/docs/*.md

From devops-skills-plugin/skills/makefile-validator:

bash

sed -n '1,220p' docs/best-practices.md
sed -n '1,220p' docs/common-mistakes.md
sed -n '1,220p' docs/bake-tool.md
rg -n "PHONY|DELETE_ON_ERROR|ONESHELL|tab|credential|mbake" docs/*.md

If shell commands are unavailable, use the environment's file-open/read actions on the same paths.

Show full SKILL.md (283 more words)Show less

Fallback Behavior

Use these only when the default validator path cannot run fully.

Constraint	Fallback action	Reporting requirement
`python3` or `pip3` unavailable	Run limited checks (`make -f <file> -n --dry-run` if `make` exists, plus focused `grep` checks)	State that `mbake` stages were skipped and coverage is reduced
`pip3 install mbake` fails (offline/proxy/index issue)	Keep syntax/custom checks that still work; defer formatter/linter stages	Report install failure and request rerun in a network-enabled environment
`make` unavailable	Continue with non-syntax stages; script already downgrades syntax stage	Explicitly note syntax coverage was skipped
`checkmake` or `unmake` unavailable	Continue; these are optional stages	Note optional lint/portability coverage not executed
target file is read-only	Provide patch suggestions only	Mark response as advisory only
command execution unavailable	Provide static review from file contents and docs	Mark result as non-executed analysis

Minimal fallback commands:

bash

# Syntax only (when make exists)
make -f <makefile-path> -n --dry-run

# Focused quick checks
grep -n "^\\.DELETE_ON_ERROR:" <makefile-path>
grep -n "^\\.PHONY:" <makefile-path>
grep -nE "^(  |    |        )[a-zA-Z@\\$\\(]" <makefile-path>

Example Outcomes Mapped to Exit Codes

Clean Result (`exit 0`)

text

Errors:   0
Warnings: 0
Info:     2
✓ Validation PASSED

Warning-Only Result (`exit 1`)

text

Errors:   0
Warnings: 3
Info:     1
⚠ Validation PASSED with warnings

Error Result (`exit 2`)

text

Errors:   2
Warnings: 1
Info:     0
⚠ Validation FAILED - errors must be fixed

Troubleshooting Quick Start

Verify required tools:

bash

command -v python3 pip3 make

Isolate GNU make syntax failures:

bash

make -f <makefile-path> -n --dry-run

Check likely tab-indentation violations:

bash

grep -nE "^(  |    |        )[a-zA-Z@\\$\\(]" <makefile-path>

Rerun validator with plain output and capture log:

bash

NO_COLOR=1 bash scripts/validate_makefile.sh <makefile-path> > /tmp/makefile-validator.log 2>&1
echo "exit=$? log=/tmp/makefile-validator.log"

If mbake install keeps failing, validate in a network-enabled shell or with an internal PyPI mirror, then rerun the full validator.

Skill Paths

text

makefile-validator/
├── SKILL.md
├── scripts/
│   └── validate_makefile.sh
├── docs/
│   ├── best-practices.md
│   ├── common-mistakes.md
│   └── bake-tool.md
└── examples/
    ├── good-makefile.mk
    └── bad-makefile.mk

Done Criteria

This skill update is complete when all are true:

Trigger guidance is explicit and easy to identify.
Execution flow is deterministic (preflight -> run -> interpret -> docs -> rerun).
"How to open docs" instructions include exact commands and paths.
Example outcomes are explicitly tied to exit codes (0, 1, 2).
Fallback behavior is documented for missing tools and constrained environments.
Troubleshooting quick-start is concise and runnable.
Frontmatter name and description remain unchanged.

Files

SKILL.md and 7 other files (scripts) in devops-skills-plugin/skills/makefile-validator of akin-ozer/cc-devops-skills.

SKILL.md
docs/bake-tool.md
docs/best-practices.md
docs/common-mistakes.md
examples/bad-makefile.mk
examples/good-makefile.mk
scripts/test_validate.sh
scripts/validate_makefile.sh

Open the folder on GitHubat commit 276af75

Compare with similar skills

Makefile Validator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Makefile Validator compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Makefile Validator this skillakin-ozer/cc-devops-skills	319	—	~1.8k	Automated safety check: Pass	Apache-2.0	2 mo ago
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop	5.3k	1 repos	~2.2k	Automated safety check: Pass	MIT	28 days ago
Summarise Ecosystem Resultsastral-sh/ruff	50k	1 repos	~2.2k	Automated safety check: Pass	MIT	today
Minimizing Ty Ecosystem Changesastral-sh/ruff	50k	—	~4.6k	Automated safety check: Pass	MIT	today
Babysit PR To Pass CIsgl-project/sglang	37k	2 repos	~3k	Automated safety check: Pass	Apache-2.0	today
Rust Best Practicesfarm-fe/farm	5.6k	3 repos	~1.1k	Automated safety check: Pass	MIT	16 days ago

Similar skills

Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
5.3k GitHub starsUsed in 1 repo~2.2k tokens
DevelopmentAuto-check passed
Summarise Ecosystem Results
astral-sh/ruff
Official
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
50k GitHub starsUsed in 1 repo~2.2k tokens
DevelopmentAuto-check passed
Minimizing Ty Ecosystem Changes
astral-sh/ruff
Official
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
50k GitHub stars~4.6k tokensUpdated today
DevelopmentAuto-check passed
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
37k GitHub starsUsed in 2 repos~3k tokens
DevelopmentAuto-check passed
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
5.6k GitHub starsUsed in 3 repos~1.1k tokens
DevelopmentAuto-check passed
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
13k GitHub stars~3.7k tokensUpdated 2 days ago
DevelopmentAuto-check passed

Questions about Makefile Validator

What does Makefile Validator do?

Validate, lint, audit, or check Makefiles and .mk files for errors. Makefile Validator is an agent skill from akin-ozer/cc-devops-skills.mk files for errors.

When should I use Makefile Validator?

Makefile Validator fits situations like: tasks that involve Linting and formatting.

How do I install Makefile Validator in Claude Code?

Run `npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a claude-code`. Or copy the skill folder (devops-skills-plugin/skills/makefile-validator in akin-ozer/cc-devops-skills) into .claude/skills/makefile-validator in your project. Claude Code loads it when a task matches its description.

How do I install Makefile Validator in Codex?

Run `npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a codex`. Or copy the skill folder (devops-skills-plugin/skills/makefile-validator in akin-ozer/cc-devops-skills) into .agents/skills/makefile-validator in your project. Codex loads it when a task matches its description.

Can I use Makefile Validator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akin-ozer/cc-devops-skills --skill makefile-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/makefile-validator, .gemini/skills/makefile-validator, .github/skills/makefile-validator and .opencode/skills/makefile-validator in your project.

What does Makefile Validator need to run?

Going by SKILL.md and its folder, Makefile Validator needs a shell for the scripts in its folder and the command-line tools its instructions call (bash, make, rg and pip3). Our summary lists: Python 3; A Bash shell.

Does Makefile Validator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Makefile Validator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Makefile Validator use?

Makefile Validator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Makefile Validator use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Makefile Validator?

Skills that share tags, products or a category with Makefile Validator: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Summarise Ecosystem Results (astral-sh/ruff, 50k stars), Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars) and Babysit PR To Pass CI (sgl-project/sglang, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Makefile Validator?

akin-ozer (a GitHub user) maintains it in akin-ozer/cc-devops-skills, which has 319 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on July 26, 2026.

Source: akin-ozer/cc-devops-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Makefile Validator

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Makefile Validator

Overview

Trigger Guidance

Trigger Phrases

Non-Trigger Examples

Deterministic Execution Model

Step 1: Preflight

Step 2: Baseline Validation (Default Path)

Step 3: Interpret Output and Exit Code

Step 4: Progressive Reference Loading

Step 5: Fix + Rerun Loop

How to Open Docs

Fallback Behavior

Example Outcomes Mapped to Exit Codes

Clean Result (exit 0)

Warning-Only Result (exit 1)

Error Result (exit 2)

Troubleshooting Quick Start

Skill Paths

Done Criteria

Files

Compare with similar skills

Similar skills

More from akin-ozer/cc-devops-skills

Related

Questions about Makefile Validator

Clean Result (`exit 0`)

Warning-Only Result (`exit 1`)

Error Result (`exit 2`)