tdd:write-tests

Generate unit and integration tests for unstaged git diffs or the latest commit.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill tdd-write-tests-luicabref97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd:write-tests
Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/tdd-write-tests
Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill tdd-write-tests-luicabref97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of ensuring local code changes are covered by tests, reducing the manual effort of identifying missing coverage and writing or orchestrating tests for unstaged changes or the latest commit.

Core Features & Use Cases

  • Analyze local changes: Detect changed and untracked files from git, filter to code, and summarize modified logic and complexity.
  • Run and verify tests: Discover how to run the project's test commands, execute full and single-test runs, and generate coverage baselines.
  • Agent-driven test creation: For complex or multi-file changes, launch coverage-reviewer and developer agents to propose and implement test cases while preserving existing tests.
  • Use case: After a feature or refactor, run the Skill to produce prioritized test cases and either automatically create tests for simple single-file changes or coordinate agents to add tests for larger changes.

Quick Start

Run the tdd:write-tests skill to analyze the current git diff and generate or orchestrate tests covering critical business logic.

Frequently Asked Questions about tdd:write-tests

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

FAQPage Schema
How do I automatically generate tests for local git diffs?

To automatically generate tests for local git diffs, you can use an agent-driven workflow that analyzes unstaged changes and untracked files, checks existing coverage, and orchestrates test creation for modified business logic.

Can I add unit tests for code changes without overwriting my existing test suite?

Yes, agent-driven test generation can analyze your latest commit or uncommitted changes and add new unit and integration test cases while strictly preserving your existing tests.

What is the best way to ensure complex multi-file code changes have test coverage?

The best way to ensure complex multi-file changes have test coverage is orchestrating coverage-reviewer and developer agents that analyze modified logic, propose prioritized test cases, and implement them across affected files.

How does an agent orchestration workflow handle test generation for untracked files?

An agent orchestration workflow handles test generation by filtering untracked and modified files from git diffs, discovering project test commands, running isolated executions to establish coverage baselines, and generating targeted tests.

Does automated test generation work if I only have staged changes in my latest commit?

Yes, automated test generation works on staged changes by falling back to analyze the latest commit when nothing is left uncommitted, ensuring recent code modifications are still covered by new tests.

How to run isolated test executions when generating tests for unstaged code changes?

To run isolated test executions during test generation, the system discovers your project's test commands, executes single-test runs for affected files, and verifies new cases against the full test suite.