new-integ

Scaffold a CDK integration test fixture with deploy/destroy verification.

97|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/go-to-k/cdkd --skill new-integ
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-integ
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/new-integ
Command: npx skills add https://github.com/go-to-k/cdkd --skill new-integ

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a new integration test fixture for cdkd, enabling rapid end-to-end testing of CDK apps by provisioning a minimal stack and a verification workflow.

Core Features & Use Cases

  • Generates a minimal CDK app scaffold tailored for integration tests.
  • Provides a ready-to-run verification script (verify.sh) and test structure.
  • Guides users to add resources and write functional checks for deploy/destroy cycles.

Quick Start

Run the scaffold with a kebab-case test name to generate a minimal CDK test fixture.

Frequently Asked Questions about new-integ

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

FAQPage Schema
How do I scaffold integration tests for CDK apps?

Scaffolding integration tests for CDK apps involves generating a minimal stack and verification workflow. This creates a structured fixture with bin/app.ts, lib/<test-name>-stack.ts, and a verify.sh script for deterministic state management and functional assertions.

What is a cdkd integration test fixture and when do I need it?

A cdkd integration test fixture is a minimal CDK app structure for end-to-end deploy/destroy testing. You need it to verify CDK apps through automated provisioning, deterministic state management, cleanup, and functional assertions.

How do I set up an end-to-end verification workflow for CDK deploy and destroy cycles?

Set up an end-to-end verification workflow by generating a verify.sh script that performs deterministic state management, cleanup, and functional assertions. This script runs alongside a synthable CDK app scaffold to automate deploy and destroy testing.

What naming format is required for creating a CDK integration test scaffold?

Creating a CDK integration test scaffold requires a kebab-case test name. This name generates the test directory structure at tests/integration/<test-name>/ and the corresponding lib/<test-name>-stack.ts file.

What files and configurations are generated when scaffolding a CDK integration test?

Scaffolding a CDK integration test generates tests/integration/<test-name>/ with bin/app.ts and lib/<test-name>-stack.ts. It also creates synthable cdk.json, package.json, tsconfig.json configurations, and a verify.sh script for functional checks.

Can I run build commands automatically within my CDK integration test scaffold?

Yes, the CDK integration test scaffold enforces a structured setup that includes running vp run build commands. This ensures the generated CDK app and dependencies are compiled before executing deploy and destroy verification checks.