build-all

Build backend and frontend projects sequentially from a configuration file.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/LeoHeo/dev-squad --skill build-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-all
Source: https://github.com/LeoHeo/dev-squad/tree/main/skills/build-all
Command: npx skills add https://github.com/LeoHeo/dev-squad --skill build-all

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the sequential building of both backend and frontend projects, streamlining the development and deployment pipeline.

Core Features & Use Cases

  • Sequential Project Building: Executes build commands for backend (Gradle/Maven) and frontend (npm) projects in a defined order.
  • Configuration-Driven: Reads project configurations from .claude/project-config.json to determine directories and project types.
  • Error Reporting: Reports success or failure for each build step and provides analysis for failures.
  • Use Case: After making changes to both your Spring Boot backend and Nuxt.js frontend, use this Skill to ensure both are built correctly and in the right order before proceeding to testing or deployment.

Quick Start

Build all projects sequentially based on the configuration file.

Frequently Asked Questions about build-all

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate building both frontend and backend projects sequentially?

Sequential project building is automated by reading a `.claude/project-config.json` configuration file to determine directories and project types, then executing backend and frontend build commands in a defined order.

Does the build automation support Spring Boot Gradle and Nuxt.js npm projects?

Yes, Spring Boot builds using Gradle or Maven and Nuxt.js builds using npm are supported, alongside Next.js, Vite, Node.js, Go, and Rust project types configured within the project file.

What is the best way to handle build failures across multiple project types?

Handling build failures involves reporting success or failure for each sequential step and providing automated failure analysis to pinpoint issues across backend and frontend project builds.

Do I need a specific project configuration file to build multiple projects?

Yes, you need a `.claude/project-config.json` file to define project directories and types, which drives the build sequence and ensures correct execution order for all configured projects.

Can I use this to build Go and Rust backend projects with a Vite frontend?

Yes, Go and Rust backend projects can be built sequentially alongside Vite frontend projects, provided the specific project directories and types are correctly declared in the configuration file.