validate-build
The validate-build command detects a project's build system (Node.js, Python, Go, Rust, or others) and executes appropriate compilation or transpilation checks. Use this before committing code to catch build failures early, verify that build artifacts are generated correctly, and identify warnings or errors with suggested fixes.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/validate-build.md -o ~/.claude/commands/validate-build.mdvalidate-build.md
# Validate Build
Validate that the project builds successfully. Run BEFORE commits to catch build failures early.
## Phase 1: Detect Build System
Identify the project's build system:
```bash
# Check for common build configurations
ls package.json Makefile setup.py pyproject.toml go.mod Cargo.toml CMakeLists.txt 2>/dev/null
```
## Phase 2: Run Build Commands
Based on detected system:
### Node.js/TypeScript
```bash
npm run build 2>&1 || yarn build 2>&1 || pnpm build 2>&1 || bun run build 2>&1
```
### Python
```bash
find . -name "*.py" -exec python -m py_compile {} +
# or for packages:
pip install -e . --dry-run
```
### Go
```bash
go build ./...
```
### Rust
```bash
cargo build
```
## Phase 3: Verify Build Artifacts
Check that expected outputs exist:
- `dist/` or `build/` directory for JS/TS
- Compiled binaries for Go/Rust
- No missing dependencies
```bash
# Example for Node.js
ls -la dist/ build/ 2>/dev/null
```
## Phase 4: Check for Warnings
Parse build output for:
- Deprecation warnings
- Unused variables/imports
- Performance warnings
- Type coercion warnings
## Output Format
```
## Build Validation: [PASS/FAIL]
### Build Command
[command used]
### Result
- Exit code: [0/non-zero]
- Duration: [time if available]
### Artifacts
- [x] Output directory created
- [x] Expected files present
- [ ] Source maps generated (if applicable)
### Warnings
- [List any build warnings]
### Errors (if failed)
- [Parse and list specific errors]
- [Suggested fixes for each]
```
## Auto-Fix Suggestions
If build fails, suggest:
1. Missing dependency installation commands
2. Type errors with file:line locations
3. Syntax errors with context
4. Configuration issues
## Usage
This command ships with the project-starter plugin. Invoke with: `/project-starter:validate-build`Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, when asked to review changes, PR review, code quality check, lint, or standards audit. Focuses on quality, security, performance, and maintainability.
Expert debugging specialist for errors, test failures, crashes, segmentation faults, memory leaks, timeouts, race conditions, deadlocks, and unexpected behavior. Use PROACTIVELY when encountering any error, exception, or failing test. Performs systematic root cause analysis.
Technical documentation specialist. Use for creating README files, API documentation, architecture docs, inline comments, user guides, changelogs, migration guides, release notes, FAQs, and troubleshooting docs. MUST BE USED when documentation is needed or when code changes require doc updates.
Master coordinator for complex multi-step tasks. Use PROACTIVELY when a task involves 2+ modules, requires delegation to specialists, needs architectural planning, or involves GitHub PR workflows. MUST BE USED for open-ended requests like "improve", "enhance", "build", "scale", "refactor", "add feature", "system design", "architecture", "complex task", or when implementing features from GitHub issues.
Code refactoring specialist for improving code quality, reducing technical debt, eliminating code smells, reducing complexity, and applying design patterns. Use PROACTIVELY when code needs restructuring, simplification, tech debt reduction, or when applying DRY/SOLID principles.
Security specialist for vulnerability detection, secure coding review, and security hardening. Use PROACTIVELY when handling authentication, authorization, encryption, secrets, credentials, OAuth, JWT, CORS, headers, user input, API keys, or sensitive data. Checks for OWASP Top 10 and common vulnerabilities.
Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use PROACTIVELY when adding new features, fixing bugs, improving test coverage, creating test plans, mocking strategies, handling flaky tests, or writing integration/E2E tests.
Add tests for recently changed files or specified code