tdd-write-tests

Generate automated tests for local code changes from git diffs.

Updated Mar 10, 2026

Search Tags:#automation #git #testing #tdd #developer tools #code coverage

Ready to run

npx skills add https://github.com/Gamezar/opencode-cek --skill tdd-write-tests-gamezar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-write-tests
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/tdd/skills/tdd-write-tests
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill tdd-write-tests-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill systematically adds test coverage for your local code changes, ensuring that new features and refactored code are robustly tested.

Core Features & Use Cases

Automated Test Generation: Creates new tests for uncommitted or recently committed code changes.
Coverage Analysis: Analyzes code complexity and identifies critical business logic requiring test coverage.
Agent Orchestration: Leverages specialized agents for complex analysis and test writing when needed.
Use Case: After modifying a critical module, this Skill can automatically generate a comprehensive suite of tests to verify the changes and prevent regressions.

Quick Start

Use the tdd-write-tests skill to add tests for your current uncommitted code changes.

Frequently Asked Questions about tdd-write-tests

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

FAQPage Schema

How do I automate test generation for local code changes?▼

Automated test generation for local code changes analyzes git diffs and file complexity to orchestrate test writing for critical business logic. It systematically adds coverage to ensure modified or refactored code is robustly tested against regressions.

What is the best way to add test coverage for uncommitted git modifications?▼

The best way to add test coverage for uncommitted git modifications is using a multi-agent system that analyzes code complexity. It identifies critical business logic and orchestrates specialized reviewer and developer agents to write tests for modified files.

Can I generate tests for complex multi-file code modifications?▼

Yes, you can generate tests for complex multi-file code modifications. The system leverages specialized reviewer and developer agents to orchestrate comprehensive test writing when handling modifications spanning across multiple files.

How does code complexity analysis identify critical business logic for testing?▼

Code complexity analysis identifies critical business logic by evaluating git diffs and file structures. This mechanism ensures automated test generation prioritizes writing tests for the most impactful and complex areas of your code modifications.

Does automated test writing work with recently committed code changes?▼

Yes, automated test writing works with both uncommitted and recently committed code changes. It evaluates the git diff to generate a comprehensive suite of tests to verify modifications and prevent future regressions.

When should I use a multi-agent system for writing tests?▼

You should use a multi-agent system for writing tests when handling complex multi-file modifications. It orchestrates specialized reviewer and developer agents to systematically add robust test coverage for critical business logic requiring in-depth analysis.