build-and-format

Run npm build and format scripts across backend, frontend, and CDK components.

84|32|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill build-and-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-and-format
Source: https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation/tree/main/.claude/skills/build-and-format
Command: npx skills add https://github.com/aws-samples/review-and-assessment-powered-by-intelligent-documentation --skill build-and-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill runs build verification and code formatting across all project components.

Core Features & Use Cases

  • Automated multi-component build validation for backend, frontend, and infrastructure (CDK) synthesis.
  • Prisma-related build support including generate, type checks, and formatting.
  • Troubleshooting guidance to fix common build or format errors before PRs.

Quick Start

Run the full build sequence from the project root to verify backend, frontend, and CDK builds.

Frequently Asked Questions about build-and-format

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

FAQPage Schema
How do I automate build verification across frontend, backend, and CDK components?

Automated build verification orchestrates npm scripts for frontend, backend, and CDK components, running prisma:generate and build commands to validate that code changes compile successfully across the project.

What's the best way to ensure code formatting consistency before submitting a PR?

Code formatting consistency is ensured by running the format npm script across all project components, validating outputs and providing troubleshooting guidance to fix common formatting errors before PR submission.

How does Prisma generate fit into the end-to-end build process?

Prisma generate fits into the build process as a prerequisite npm script step, executing before type checks and builds to ensure the generated Prisma client is available for backend compilation and formatting validation.

Why does my CDK synthesis fail during the multi-component build sequence?

CDK synthesis can fail during the build sequence due to missing dependencies, invalid infrastructure code, or incomplete Prisma generation, and the skill provides troubleshooting guidance to resolve these common build errors.

Can I run backend and frontend builds independently instead of the full build sequence?

The full build sequence runs npm scripts for backend, frontend, and CDK together, but individual component scripts can be executed independently to isolate build issues or verify specific changes during development.

Do I need to run prisma:generate separately before build and format commands?

The prisma:generate command is included in the automated build sequence alongside build and format scripts, ensuring the Prisma client is generated before type checks and compilation are executed.