Build And Format
- 1 installs
- 84 repo stars
- Updated August 4, 2026
- aws-samples/review-and-assessment-powered-by-intelligent-documentation
Build and Format is a Claude Code skill that runs build verification and Prettier formatting across the RAPID project's backend, frontend, and CDK components.
About
Build and Format runs build verification and code formatting across all RAPID project components (backend, frontend, and CDK) in dependency order so backend builds before CDK. It includes a Prisma-specific path (prisma:generate then build) after schema changes and a table mapping common errors to fixes. A developer uses it after implementing code changes, before committing, or before creating a pull request. Success means TypeScript compiles, Vite builds, the CloudFormation template synthesizes, and all code is Prettier-formatted.
- Runs build verification and code formatting across backend, frontend, and CDK in dependency order
- Includes Prisma-specific build (prisma:generate then build) after schema changes
- Maps common build errors (missing @prisma/client, CDK Docker daemon) to fixes
Build And Format by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,173 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
build-and-format capabilities & compatibility
- Capabilities
- build verification · code formatting · cdk synth
- Works with
- aws · docker
- Use cases
- ci cd · devops · testing
- Pricing
- Free
What build-and-format says it does
Run builds in dependency order (backend must build before CDK):
After successful build, consider running `/test-database-feature` if database changes were made.
npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill build-and-formatAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 84 |
| Last updated | August 4, 2026 |
| Repository | aws-samples/review-and-assessment-powered-by-intelligent-documentation ↗ |
What it does
Verify that RAPID backend, frontend, and CDK build cleanly and are Prettier-formatted before committing or opening a PR.
Who is it for?
RAPID developers verifying the build compiles and code is formatted before committing or opening a PR.
Skip if: Deploying infrastructure (use deploy-cdk-stack) or running tests beyond build verification.
When should I use this skill?
After implementing code changes, before committing, after modifying the Prisma schema, or before creating a pull request.
What you get
Backend, frontend, and CDK build without errors and all code is Prettier-formatted.
- Compiled backend and frontend
- Synthesized CDK CloudFormation template
- Prettier-formatted code
By the numbers
- Three components built (backend, frontend, CDK)
- Builds run in dependency order
Files
Build and Format Verification
Build Sequence
Run builds in dependency order (backend must build before CDK):
# 1. Backend (must be first - CDK depends on it)
cd backend
npm run build
npm run format
# 2. Frontend
cd ../frontend
npm run build
npm run format
# 3. CDK (depends on backend build)
cd ../cdk
npx cdk synthPrisma-Specific Build
After modifying backend/prisma/schema.prisma:
cd backend
npm run prisma:generate
npm run build
npm run formatCommon Errors
| Error | Solution |
|---|---|
Module not found: @prisma/client | cd backend && npm run prisma:generate |
Cannot find module '../backend/...' (CDK) | Build backend first |
Docker daemon not running (CDK synth) | Start Docker Desktop |
Quick Commands
| Task | Command |
|---|---|
| Backend build + format | cd backend && npm run build && npm run format |
| Frontend build + format | cd frontend && npm run build && npm run format |
| CDK synth | cd cdk && npx cdk synth |
| Prisma generate | cd backend && npm run prisma:generate |
Success Criteria
- Backend: TypeScript compiles without errors
- Frontend: Vite builds without errors
- CDK: CloudFormation template generates
- All code formatted by Prettier
After successful build, consider running /test-database-feature if database changes were made.
Related skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.485k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.485k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.170k199k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.99.3k29.7kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.74.6k29.7kFAQ
What order do builds run in?
Backend first (CDK depends on it), then frontend, then CDK synth.
What do I run after a Prisma schema change?
cd backend && npm run prisma:generate && npm run build && npm run format.