build-system
This Claude Code skill automatically detects a project's build system by checking for configuration files like package.json, pyproject.toml, or Makefile, then executes the appropriate build or test commands. Use it to streamline project compilation and testing across multiple languages and package managers including Node.js, Python, Java, Rust, and Go without manually specifying which build tool to invoke.
git clone --depth 1 https://github.com/sangrokjung/claude-forge /tmp/build-system && cp -r /tmp/build-system/skills/build-system ~/.claude/skills/build-systemSKILL.md
# Build System Skill
## 개요
프로젝트의 빌드 시스템을 자동으로 감지하고 적절한 빌드/테스트 명령어를 실행합니다.
## 지원 빌드 시스템
| 빌드 시스템 | 감지 파일 | 빌드 명령어 | 테스트 명령어 |
|------------|----------|------------|--------------|
| npm | `package.json` | `npm run build` | `npm test` |
| yarn | `yarn.lock` | `yarn build` | `yarn test` |
| pnpm | `pnpm-lock.yaml` | `pnpm build` | `pnpm test` |
| Python (pip) | `requirements.txt` | `pip install -r requirements.txt` | `pytest` |
| Python (poetry) | `pyproject.toml` | `poetry install` | `poetry run pytest` |
| Gradle | `build.gradle` | `./gradlew build` | `./gradlew test` |
| Maven | `pom.xml` | `mvn package` | `mvn test` |
| Cargo | `Cargo.toml` | `cargo build` | `cargo test` |
| Go | `go.mod` | `go build ./...` | `go test ./...` |
| Make | `Makefile` | `make` | `make test` |
## 사용법
프로젝트 루트에서 빌드 시스템을 자동 감지하고 실행합니다.
### 빌드
```bash
# 자동 감지 후 빌드
/build
# 특정 명령어로 빌드
/build --cmd="npm run build:prod"
```
### 테스트
```bash
# 자동 감지 후 테스트
/test
# 특정 테스트만 실행
/test --filter="unit"
```
## 감지 우선순위
1. `package-lock.json` → npm
2. `yarn.lock` → yarn
3. `pnpm-lock.yaml` → pnpm
4. `pyproject.toml` → poetry
5. `requirements.txt` → pip
6. `Cargo.toml` → cargo
7. `go.mod` → go
8. `build.gradle` → gradle
9. `pom.xml` → maven
10. `Makefile` → make
## 커스터마이징
프로젝트별로 `.claude/config.json`에서 빌드 명령어를 오버라이드할 수 있습니다:
```json
{
"build": {
"command": "npm run build:custom",
"test_command": "npm run test:ci"
}
}
```Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /update-codemaps and /update-docs, generates docs/CODEMAPS/*, updates READMEs and guides.
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.