build-check

AppleLamps's avatarfrom AppleLamps

Run build and lint verification before deployment. Use when user mentions "check build", "verify", "pre-deploy", "ready to deploy", or asks to validate the project.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 7, 2026
[CI and CD]

When & Why to Use This Skill

This Claude skill automates pre-deployment verification by executing linting, type-checking, and production build processes. It ensures code stability and quality before shipping to production, helping developers catch errors early and maintain a robust deployment pipeline for Next.js and TypeScript projects.

Use Cases

  • Pre-deployment validation: Automatically run 'npm run build' and 'npm run lint' to ensure the project is stable before a release.
  • Automated code quality checks: Perform static analysis and type-checking using 'npx tsc' to identify potential runtime errors and syntax issues.
  • Build error debugging: Parse complex build logs to identify specific file paths and line numbers for faster troubleshooting and resolution.
  • Environment readiness check: Verify that the project is 'ready to deploy' by confirming all build artifacts are generated successfully.
namebuild-check
descriptionRun build and lint verification before deployment. Use when user mentions "check build", "verify", "pre-deploy", "ready to deploy", or asks to validate the project.
allowed-toolsRead, Glob, Grep, Bash

Build Check

Pre-deployment verification for the Next.js portfolio site.

Instructions

  1. Run lint check:

    npm run lint

  2. Run production build:

    npm run build

  3. If errors occur:

    • Parse error messages
    • Identify affected files
    • Suggest specific fixes

  4. Report results summary:

    • Lint warnings/errors count
    • Build success/failure
    • Bundle size if available

Default Commands

  • Lint: npm run lint
  • Build: npm run build
  • Type check: npx tsc --noEmit

Examples

  • "Check if the build passes"
  • "Verify before deploying"
  • "Run pre-deploy checks"

Guardrails

  • Do NOT modify files to fix errors without user confirmation
  • Report issues clearly with file paths and line numbers
  • If build fails, ask user before attempting fixes