hunt-bugs

Deploy real CDK apps to identify and fix latent cdkd bugs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-cli, git, and includes scripts (resource) components.

What problem does it solve?

Proactively hunt for cdkd bugs in real-world deployments by deploying CDK apps that exercise common-but-untested AWS resources and CloudFormation notations, then identify and fix issues before they reach production.

Core Features & Use Cases

  • Deploys real CDKD test apps to surface latent bugs across AWS resources and notations.
  • Enforces a strict cleanup workflow via a per-owner sentinel gate to ensure resources are destroyed after testing.
  • Supports parallel bug-hunt runs across multiple stacks while preventing resource orphaning.

Quick Start

Scaffold a bug-hunt workflow, deploy a set of throwaway CDK stacks in parallel, observe the results, and destroy all resources when finished.

Frequently Asked Questions about hunt-bugs

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

FAQPage Schema
How do I proactively hunt for bugs in real CDK deployments before they reach production?

You can proactively hunt for bugs in real CDK deployments by deploying throwaway CDK apps to exercise AWS resources and CloudFormation notations, then identifying and fixing latent issues before production release.

What's the best way to run parallel bug hunts on AWS CloudFormation stacks without orphaning resources?

Run parallel bug hunts on AWS CloudFormation stacks safely by using a per-owner sentinel gate mechanism that arms, verifies, and releases a strict cleanup workflow to ensure all resources are destroyed after testing.

Do I need real AWS access and the AWS CLI to test untested CDK patterns?

Yes, you need real AWS access and the AWS CLI configured, along with git, because this testing approach deploys actual CDK apps to exercise real AWS resources and CloudFormation notations rather than simulating them.

How does the sentinel mechanism enforce cleanup during destructive CDK workflows?

The sentinel mechanism enforces cleanup during destructive CDK workflows by acting as a per-owner gate that must arm, verify, and release, ensuring resources are tracked and destroyed after parallel bug-hunt runs to prevent orphaning.

Can I use this bug hunt approach to test common-but-untested CDK loops and destructive workflows?

Yes, this bug hunt approach specifically targets common-but-untested CDK patterns, repeated loops, and destructive workflows by deploying real stacks in parallel with safeguards to surface latent developmental bugs.

What are the limitations of deploying real CDK apps for bug hunting?

Deploying real CDK apps for bug hunting requires real AWS access, active git repositories, and strict adherence to the sentinel cleanup gate, meaning incomplete workflow execution risks orphaning deployed AWS resources.