generate
/generate
Generate tests: policy assertions for a synthesized CDK stack (queues have dead-letter queues, functions have timeouts, tables have recovery, no * on *), and a unit-test skeleton for a Lambda handler built on event fixtures. Use when the user asks for tests for a handler or for infrastructure checks.
- Author
- Alejo2075 ↗
- Repository
- claude-code-aws ↗
- Licence
- MIT
- Last repository change
- 31.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Generate tests: policy assertions for a synthesized CDK stack (queues have dead-letter queues, functions have timeouts, tables have recovery, no * on *), and a unit-test skeleton for a Lambda handler built on event fixtures. Use when the user asks for tests for a handler or for infrastructure checks.
Arguments
/generate cdk-assertions <stack> | handler <file> <kind>
Original author description
Generate tests: policy assertions for a synthesized CDK stack (queues have dead-letter queues, functions have timeouts, tables have recovery, no * on *), and a unit-test skeleton for a Lambda handler built on event fixtures. Use when the user asks for tests for a handler or for infrastructure checks.
How it works
- Side effects
- Preconditions and inputs
- Read-only reconnaissance
- Steps
- Agents and tools
- Output
- Failure, permission, cost, and safety handling
SKILL.md preview
---
name: generate
description: Generate tests: policy assertions for a synthesized CDK stack (queues have dead-letter queues, functions have timeouts, tables have recovery, no * on *), and a unit-test skeleton for a Lambda handler built on event fixtures. Use when the user asks for tests for a handler or for infrastructure checks.
argument-hint: "cdk-assertions <stack> | handler <file> <kind>"
disable-model-invocation: true
allowed-tools: Bash(node ${CLAUDE_PLUGIN_ROOT}/dist/cli.mjs generate *)
---
# Generate tests
Writes test files from deterministic generators. You then add the cases that need domain knowledge.
## Side effects
`local-write` with `--write`: creates files under `test/` and never overwrites. Without `--write` it only shows what it would create. Manual invocation because it writes files.
## Preconditions and inputs
- `cdk-assertions <stack>`: a synthesized `cdk.out` (run `/aws-infrastructure:synth`). The assertions read the template, so they check policy and keep holding while values change.
- `handler <file> <kind>`: the handler file and an event kind (`sqs`, `apigw-http-v2`, `apigw-rest-v1`, `sns`, `eventbridge`, `dynamodb-stream`, `s3`, `stepfunctions-task`).
## Read-only reconnaissance
Read the handler to see what it does with the event and with AWS before writing the extra cases.
## Steps
1. Run without `--write` and show the user what would be created.
2. After they agree, run with `--write`.
3. Replace each `TODO` with a real test: the business rule that decides success or failure, and the exact parameters of every AWS call (with a mock of the SDK client).
4. Run `/aws-testing:run --affected`.
## Agents and tools
The Bash tool, restricted to this plugin's `generate` command. No agent and no MCP server.
## Output
The files created and what each checks. Name what the generated tests do **not** cover: behavior of the deployed resources, permissions at run time, and anything in the TODO list.
## Failure, permission, cost, and safety handling
- Do not weaken or delete a generated assertion to make a test pass. If it fails, the template really breaks the policy: fix the infrastructure or discuss it with the user.
- Never put real credentials, real account ids, or real customer data in fixtures.
- Mocks are not AWS integration coverage: say so.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Alejo2075/claude-code-aws | 90 | MIT |
| jkaloger/lazyspec | 100 | MIT |
| LandonSchropp/agent-toolkit | 100 | MIT |
| magnifito/domain-name-engine | 100 | MIT |
| alirezarezvani/claude-skills | 100 | MIT |
| galyarderlabs/galyarder-framework | 100 | MIT |
| galyarderlabs/galyarder-framework | 100 | MIT |
| gabrielekarra/mcp-anything | 100 | Apache-2.0 |
| synaptiai/agent-capability-standard | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 8a932dddaadd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90review
Review the operational quality of a CDK app from its synthesized templates: dead-letter queues, visibility timeouts against function timeouts, runtime support, log retention, deletion policies, point-in-time recovery, tracing, alarms. Use when the user asks for an infrastructure… - 90routes
Show how events are routed in a synthesized CDK app: buses, rules, targets, schedules, and findings such as targets without a dead-letter queue. Use for questions about what triggers what. - 100trove-lambda
AWS Lambda handler patterns with CDK infrastructure conventions. Auto-activates when working with Lambda handler or CDK files. Covers handler structure, SQS/SNS parsing, IPC patterns, Powertools logging, and CDK best practices. Use when: lambda handler; aws lambda; sqs handler; sns handler. - 100sqs
AWS SQS message queue service for decoupled architectures. Use when creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, or integrating with Lambda. - 100cdk-stack-generator
Generate cdk stack generator operations. Auto-activating skill for AWS Skills. Triggers on: cdk stack generator, cdk stack generator Part of the AWS Skills skill category. Use when working with cdk stack generator functionality. Trigger with phrases like "cdk stack generator",… - 100aws-serverless-patterns
AWS Lambda, API Gateway, DynamoDB, Step Functions, EventBridge patterns and best practices. Use when building or reviewing serverless backends, CDK infrastructure, or Lambda functions.