lang-makefile
Skill5 starsChanged 46 days agoMITView on GitHub
use this when writing or reviewing Makefile / GNUmakefile. thin skill. do not use instead of the language skill for the code the Makefile builds.
- Pipes a download into a shell
- Deletes or force-pushes
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- maintainers/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- buying-researcherSkill
- cursor-cloud-agents-whenSkill
- debug-anthropicSkill
- debug-pocockSkill
- debugSkill
- discover-the-ideaSkill
- docs-google-styleSkill
- golang-safetySkill
- golang-securitySkill
- golang-testingSkill
- grok-acpSkill
- host-config-pyinfraSkill
- lang-cppSkill
- lang-csharpSkill
- lang-cSkill
- lang-dartSkill
- lang-dockerSkill
- lang-goSkill
- lang-javaSkill
- lang-js-tsSkill
- lang-kotlinSkill
- lang-luaSkill
- lang-phpSkill
- lang-powershellSkill
- lang-protobufSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-shellSkill
- lang-sqlSkill
- lang-swiftSkill
- lang-terraformSkill
- language-routerSkill
- lang-web-markupSkill
- modern-pythonSkill
- pr-reviewSkill
- sdlc-artifactsSkill
- sdlc-onboardingSkill
- security-hardeningSkill
- shell-safetySkill
- tddSkill
- tracker-sdlcSkill
- ui-craftSkill
- ux-designSkill
- verify-before-doneSkill
- yagniSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Run the changed target. Dry-run first when the target is destructive.
- Distinctive: line 51
No unquoted destructive globs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Make
No scripts/. The language being built still loads its own skill.
Process skills that may load with this one: load-with list.
Iron law
Every recipe is a real dependency graph. Tabs. Quoted variables.
Tooling / verify
make -n <target> # print, do not run
make <target> # then run the target you changedConfirm only intended files changed.
Idioms a linter misses
.PHONYfor non-file targets.- Automatic vars (
$@,$<,$^) instead of repeating names. - One source of truth for flags (
CFLAGS,GOFLAGS). - Recipe lines fail closed. Do not hide errors with a leading
-unless you say why. - The default target is what a stranger should run.
Errors
- A failed recipe stops the build.
.DELETE_ON_ERRORif the project already uses it.
Testing
- Run the changed target. Dry-run first when the target is destructive.
PR review
- Tabs vs spaces in recipes.
rm -rfis quoted and${DIR:?}-style guarded.- Recursive make is not introduced as a new architecture.
Security
- No
curl | shin a recipe. - No unquoted destructive globs.
Always
.PHONY. Quoted paths.make -non destructive targets.
Ask first
- Generating files outside the repo.
- A new recursive make of another tree.
Never
- Unquoted
rm -rf $(DIR). - Treating Make as a list of shell scripts with no graph.
Red flags
- "Make is just a script list"
- "The dash prefix makes it more reliable"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

