メニュー
Use when building naverworks binaries — single-platform or cross-platform artifacts with ldflags version metadata. Triggers on "빌드", "build", "/build". If you need test results only, use the test skill. If you need to publish a release tag, use deploy or version.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | build |
| description | Use when building naverworks binaries — single-platform or cross-platform artifacts with ldflags version metadata. Triggers on "빌드", "build", "/build". If you need test results only, use the test skill. If you need to publish a release tag, use deploy or version. |
이 스킬은 AI 에이전트가 직접 실행한다. 로컬 또는 크로스 플랫폼 바이너리를 빌드한다.
| 입력 | 필수 여부 | 형식 | 설명 |
|---|---|---|---|
| 인자 | 선택 | enum: local(기본), all | local은 현재 플랫폼, all은 5개 플랫폼 크로스 빌드 |
| 필드 | 설명 |
|---|---|
mode | local 또는 all |
artifacts | 생성된 바이너리/아카이브 경로 목록 |
version_metadata | ./naverworks version 결과 (JSON) |
go vet 및 go test가 통과한다.local: ./naverworks 실행 파일이 생성되고 naverworks version이 동작한다.all: 5개 플랫폼 아카이브(4 tar.gz + 1 zip)가 dist/에 생성된다.all이면 5개 플랫폼 크로스 빌드.local: 현재 플랫폼 빌드 → Phase 2aall: 5개 플랫폼 크로스 빌드 → Phase 2bgo vet ./...
go test ./... -count=1
하나라도 실패하면 중단한다.
make build
ls -lh naverworks
./naverworks version
버전 추출 — v prefix를 제거하여 goreleaser/deploy와 일치시킨다:
git describe --tags --abbrev=0 2>/dev/null
→ 태그가 있으면 v prefix 제거하여 VERSION에 저장 (예: v0.1.0 → 0.1.0)
→ 태그가 없으면 dev 사용
goreleaser 확인:
command -v goreleaser
goreleaser가 있으면 (권장):
goreleaser release --clean --skip=publish --snapshot
goreleaser가 없으면 각 플랫폼을 수동으로 빌드한다. LDFLAGS 구성, 플랫폼별 GOOS/GOARCH 명령, 아카이브 포맷은 references/cross-build-commands.md를 참조한다.
로컬 빌드:
빌드 완료:
naverworks (6.1MB)
버전: {"version":"dev","commit":"abc1234","build_date":"..."}
크로스 빌드:
빌드 완료: 5개 플랫폼
dist/naverworks_0.1.0_linux_amd64.tar.gz 2.6MB
dist/naverworks_0.1.0_linux_arm64.tar.gz 2.4MB
dist/naverworks_0.1.0_darwin_amd64.tar.gz 2.6MB
dist/naverworks_0.1.0_darwin_arm64.tar.gz 2.5MB
dist/naverworks_0.1.0_windows_amd64.zip 2.7MB
Use when setting up or troubleshooting naverworks CLI multi-profile authentication, including profile creation, OAuth/JWT login, and CI/CD auth configuration. Triggers on "naverworks 프로필", "naverworks 인증", "NW_PROFILE". If the task is executing NAVER WORKS API commands, use the naverworks-cli skill. If the task is build or release automation, use the build or deploy skill.
Use when adding or refactoring `naverworks-cli` commands or internals and you need to manage project-specific code reuse, helper extraction, duplication cleanup, or reuse exceptions. Reviews hotspot-heavy `cmd/` and `internal/` code, decides whether to reuse an existing helper, extract a new shared helper, keep logic local, or grant a time-bounded waiver, and records catalog/lifecycle/scorecard updates. If you only need build, test, deploy, release, version, profile, or commit workflows, use the existing project-local skills instead.
Use when releasing a new version of naverworks — runs preflight checks, creates and pushes a SemVer tag, and verifies the GitHub Actions release workflow that builds artifacts and publishes npm packages. Triggers on "배포", "릴리스", "deploy", "release", "/deploy". If you only need to inspect or create tags, use version. If you only need local binaries, use build.
Use when verifying the naverworks codebase — runs unit, integration, and e2e test layers with go test, go vet, and build smoke check. Triggers on "테스트", "test", "/test". Covers test pyramid (unit/integration/e2e) with real functionality verification. For local binaries, use build. For releasing, use deploy. For managing existing releases, use release. For version inspection or tag creation, use version.
Use when inspecting naverworks version state or creating/pushing release tags directly. Triggers on "버전", "version", "/version", "bump". If you want guarded preflight checks plus release monitoring, use deploy. If you only need local binaries, use build.
Manage GitHub Releases for naverworks — view, edit, delete, and rollback published releases using gh CLI. Triggers on "릴리스 관리", "release manage", "release edit", "release delete", "release rollback". If you need to create a new release (tag + push + publish), use deploy. For local binaries, use build. For running tests, use test. For version inspection or tag creation, use version.