From dev-squad
Use when building both backend and frontend projects sequentially - runs gradle build then npm build and reports results
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-squad:build-allThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
모든 대상 디렉토리를 순서대로 빌드해줘.
모든 대상 디렉토리를 순서대로 빌드해줘.
.claude/project-config.json을 읽어서 대상 디렉토리와 type을 확인해줘.
파일이 없으면 /start-work를 먼저 실행하라고 안내해줘.
| type | 빌드 명령어 |
|---|---|
spring-boot (gradle) | ./gradlew clean build |
spring-boot (maven) | ./mvnw clean package |
nuxt / nextjs / vite / node | npm run build |
go | go build ./... |
rust | cargo build --release |
| 기타 | AskUserQuestion으로 빌드 명령어 확인 |
실패 시 원인을 분석하고 수정 방안을 제시해줘.
npx claudepluginhub leoheo/dev-squad --plugin dev-squadDetects the project's build system (npm, yarn, pnpm, pip, poetry, gradle, maven, cargo, go, make) and runs build/test commands. Useful for automating project setup and continuous integration.
Guides Maven build lifecycles (default, clean, site), phases, goals, profiles, and customization via XML for Java projects. Includes common commands and bindings.
Assists with Maven for Java: initializes projects, configures pom.xml, manages dependencies and scopes, sets up builds/plugins/profiles, troubleshoots errors.