tdd

Manage iterative code changes and automated testing for Kagenti agents.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill tdd-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/kagenti/kagenti --skill tdd-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the test-driven development process for Kagenti agents, ensuring robust and reliable code through iterative testing and automated workflows.

Core Features & Use Cases

  • Workflow Automation: Guides developers through issue-first, PR-first, or local development flows.
  • Integrated Testing: Orchestrates local (Kind) and remote (CI, HyperShift) test execution.
  • Use Case: When a bug is reported in a GitHub issue, this Skill helps you quickly set up a development environment, write tests, implement the fix, and ensure it passes CI before merging.

Quick Start

Initiate a test-driven development cycle for a new feature by running the tdd skill with a local task description.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I automate test-driven development for agent development workflows?

You can automate test-driven development for agent workflows by guiding iterative code changes and running automated tests across local and remote environments before integrating PRs.

What is the best way to manage CI/CD testing for Kagenti agents across Kind and HyperShift?

The best way to manage CI/CD testing for Kagenti agents is to orchestrate test execution across local Kind clusters and remote HyperShift environments, integrating root cause analysis and commit policies.

How do I fix a bug reported in a GitHub issue using a test-driven workflow?

To fix a bug from a GitHub issue using a test-driven workflow, initiate an issue-first development flow to set up the environment, write tests, implement the fix, and validate CI.

Do I need a local Kind cluster to run automated tests during Kagenti development?

You need a local Kind cluster or remote CI and HyperShift environments to orchestrate the automated testing required for validating iterative code changes during Kagenti development.

Can I use a PR-first workflow for integrating code changes in CI/CD pipelines?

You can use a PR-first workflow to integrate code changes in CI/CD pipelines, supporting automated testing and root cause analysis to ensure robust merging for Kagenti agents.