---

name: auto-build description: Skill for auto-detecting project type and executing builds. Suggests builds after code changes, proposes fixes for build errors. Supports Node.js, Rust, Python, Go, and Makefile projects.

Auto Build Skill

Automatically detects project configuration and executes appropriate build commands.

Auto-Suggestion Triggers

Project Type Detection

Package Manager Detection (Node.js)

Copy# Priority order
if [ -f "pnpm-lock.yaml" ]; then
    PM="pnpm"
elif [ -f "yarn.lock" ]; then
    PM="yarn"
elif [ -f "bun.lockb" ]; then
    PM="bun"
else
    PM="npm"
fi

Build Commands

Node.js Projects

Copy# Install dependencies (if needed)
$PM install

# Standard build
$PM run build

# Production build
$PM run build:prod  # or NODE_ENV=production $PM run build

# Clean build
rm -rf dist node_modules/.cache && $PM run build

Rust Projects

Copy# Fetch dependencies
cargo fetch

# Debug build
cargo build

# Release build
cargo build --release

# Clean build
cargo clean && cargo build --release

Python Projects

Copy# Virtual environment (with pyproject.toml)
poetry install  # or pip install -e .

# Build
python -m build

# Create wheel
pip wheel .

Go Projects

Copy# Download dependencies
go mod download

# Build
go build

# Production build
CGO_ENABLED=0 go build -ldflags="-s -w"

Makefile Projects

Copy# Standard build
make

# Clean build
make clean && make

# Specific targets
make build
make release

Build Flow

Copy┌─────────────────┐
│ Detect Project  │
└────────┬────────┘
         ↓
┌─────────────────┐
│ Check Deps      │ ──→ Install if missing
└────────┬────────┘
         ↓
┌─────────────────┐
│ Execute Build   │
└────────┬────────┘
         ↓
    ┌────┴────┐
    ↓         ↓
┌───────┐ ┌───────┐
│Success│ │Failed │ ──→ Analyze & suggest fix
└───────┘ └───────┘

Error Handling

Common Errors and Solutions

Error Analysis Flow

1. Parse error message
2. Identify error type
3. Locate file and line
4. Propose fix
5. Apply fix and rebuild after user confirmation

Usage Scenarios

Scenario 1: After Code Changes

CopyAI: Code has been modified. Shall I run a build?

# Detection result
Project type: Node.js (TypeScript)
Package manager: pnpm

# Execute
pnpm run build

Scenario 2: After Adding Dependencies

CopyAI: New dependencies added. Shall I install and build?

# Execute
pnpm install && pnpm run build

Scenario 3: On Build Error

CopyAI: Build error occurred.

Error: Cannot find module '@types/node'

Proposed fix:
1. Install @types/node
2. Rebuild

Proceed?

# Execute
pnpm add -D @types/node && pnpm run build

Scenario 4: Clean Build

CopyAI: Config file changed. Clean build recommended.

# Execute
rm -rf dist .cache && pnpm run build

Project-Specific Configuration

Build settings can be specified in CLAUDE.md or PROJECT.md:

Copy## Build Settings
- Build command: `npm run custom-build`
- Test command: `npm run test:all`
- Production build: `npm run build:prod`
- Pre-build: `npm run prebuild`

Decision Criteria

When to Suggest Build

• Source code (.ts, .js, .rs, .py, .go) modified
• Config files (tsconfig.json, Cargo.toml, etc.) modified
• Dependency files (package.json, etc.) modified
• User mentions "build" or "compile"

When to Suggest Clean Build

• Build config files modified
• Dependency versions changed
• Previous build failed
• Cache-related errors occurred

Notes

• Check for unsaved changes before building
• Show progress for long builds
• Prompt for selection when multiple build targets exist
• Consider CI/CD environment consistency