/build

> Detect project type, compile, and report errors with actionable fixes.

170 stars

Best use case

/build is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Detect project type, compile, and report errors with actionable fixes.

Teams using /build should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/build/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/development/build/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/build/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How /build Compares

Feature / Agent/buildStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

> Detect project type, compile, and report errors with actionable fixes.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /build

> Detect project type, compile, and report errors with actionable fixes.

## Usage
```
/build [path] [--clean] [--verbose] [--target <env>]
```

## What It Does
Scans the project root for config files (mix.exs, package.json, Cargo.toml, go.mod, Makefile), runs the appropriate build command, captures output, and reports errors with structured diagnostics. Handles monorepos by detecting and building each sub-project.

## Implementation
1. **Detect project type** from config files in priority order.
2. **Check prerequisites** -- verify toolchain installed, deps fetched.
3. **Clean** (if `--clean`) -- remove build artifacts.
4. **Build** -- run the build command, capture stdout/stderr/exit code/duration.
5. **Parse errors** -- extract file paths, line numbers, error types. Suggest fixes.
6. **Report** -- structured build report with errors, warnings, artifacts.

| Config File | Language | Build Command |
|-------------|----------|---------------|
| mix.exs | Elixir | `mix compile` |
| package.json | Node.js | `npm run build` |
| Cargo.toml | Rust | `cargo build` |
| go.mod | Go | `go build ./...` |
| Makefile | Make | `make` |

## Examples
```bash
# Build current project
/build

# Clean build for production
/build --clean --target prod

# Build specific sub-project in monorepo
/build engine/

# Verbose output for debugging build issues
/build --verbose --clean
```