verify-build

Verify TypeScript builds and configuration completeness for claude-code-reviewer.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill verify-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-build
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/verify-build
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill verify-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates verification of the codebase build and ensures configuration completeness and webhook ordering for claude-code-reviewer.

Core Features & Use Cases

  • TypeScript Build: verifies the project builds with npm run build
  • Config Defaults Completeness: checks that all ReviewConfig, PollingConfig, WebhookConfig, and GithubConfig fields have defaults
  • Config.yaml Documentation: ensures all ReviewConfig fields are documented in config.yaml and checks top-level mode, polling, webhook, and github sections
  • State Backfill Completeness: validates PRState fields across getOrCreate defaults, backfill loop, and V1 migration
  • Webhook Response Ordering: confirms HTTP responses precede async processing in webhook and PR handlers

Quick Start

Run the build verifier to perform all checks and report the results.

Frequently Asked Questions about verify-build

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

FAQPage Schema
How do I automate build verification and config consistency checks for a TypeScript project?

Build verification automates TypeScript project builds using npm run build and cross-checks configuration completeness against src/types.ts, src/config.ts, and config.yaml to ensure consistency and correctness across environments.

How do I validate that all TypeScript config defaults are complete before a CI build?

Validating config defaults completeness checks that all ReviewConfig, PollingConfig, WebhookConfig, and GithubConfig fields have defaults defined, preventing missing configuration values from breaking CI builds or runtime behavior.

What is the best way to ensure webhook HTTP responses precede async processing?

Webhook response ordering verification confirms HTTP responses are sent before async processing begins in webhook and PR handlers, ensuring clients receive timely acknowledgments while background tasks execute safely.

How do I check that config.yaml documents all ReviewConfig fields correctly?

Config.yaml documentation checks verify that all ReviewConfig fields are documented in config.yaml and validate top-level mode, polling, webhook, and github sections for complete configuration coverage.

How do I validate PRState field completeness across backfill loops and migrations?

State backfill completeness validation checks PRState fields across getOrCreate defaults, the backfill loop, and V1 migration paths to ensure no state fields are missing during transitions or data population.

Do I need npm run build to verify codebase configuration consistency?

Yes, npm run build is required as the verify-build process executes the TypeScript build and cross-checks against src/types.ts, src/config.ts, and config.yaml to validate structural and configuration consistency.