make

Run build, check, and test commands and return structured diagnostics.

2|Updated Sep 12, 2016
One-click install
npx skills add https://github.com/paulnsorensen/dotfiles --skill make-paulnsorensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make
Source: https://github.com/paulnsorensen/dotfiles/tree/main/claude/skills/make
Command: npx skills add https://github.com/paulnsorensen/dotfiles --skill make-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the verification of code changes by running builds, tests, and format checks in a forked subagent and returning only structured diagnostics, so noisy compile output never floods your context.

Core Features & Use Cases

  • Auto-detects the correct build system from project files and runs check, build, or test commands as needed.
  • Filters verbose output and returns structured errors in the form file:line:col with optional error codes, enabling precise navigation and CI integration.
  • Supports common workflows: /make, /build, /check, /compile, and specialized actions like /make test, /make lint, /make fmt, and /make clean.

Quick Start

From the project root, run /make to detect and execute the appropriate build or check command and receive a clean, parseable report of errors and warnings.

Frequently Asked Questions about make

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

FAQPage Schema
How do I get structured build errors instead of noisy compile output?

To get structured build errors, you can run an automated build command that filters verbose output and returns only structured diagnostics in the form file:line:col with optional error codes. This prevents noisy compile output from flooding your context.

How do I automate running tests and format checks in CI?

You can automate running tests and format checks in CI by executing build, check, and test commands with guardrails that capture and return structured errors and warnings in a consistent, machine-parseable format suitable for downstream tooling.

Can I auto-detect the correct build system for my project?

Yes, you can auto-detect the correct build system from project files to run check, build, or test commands as needed. This allows you to execute the appropriate build or check command automatically from the project root.

What build commands does the automation support?

The build automation supports common workflows including /make, /build, /check, /compile, and specialized actions like /make test, /make lint, /make fmt, and /make clean for comprehensive project verification.

Why does my build output flood the context with verbose logs?

Verbose build output floods context because standard compile commands emit all logs directly. Running builds and tests in a forked subagent captures and returns only structured errors and warnings, preventing noisy output from flooding your context.

Does this work for CI integration with machine-parseable diagnostics?

Yes, it works for CI integration by surfacing diagnostics in a consistent, machine-parseable format. It provides guardrails for command execution, error collection, and result formatting, ensuring predictable output for downstream tooling.