Skip to content
Back to skills

Test Driven Agent

ASecurity

An advanced testing protocol that enforces TDD (Test Driven Development) and self-healing tests.

  • 207 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 7, 2026
developmentbashtestingapi

Works with

  • api

Security analysis

A100/100

Pro scans all 9 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add NeverSight/skills_feed --skill test_driven_agent --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Test Driven Agent?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Test Driven Agent
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neversight-test-driven-agent/badge)](https://www.skillsdirectory.com/skills/neversight-test-driven-agent)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: test_driven_agent
description: An advanced testing protocol that enforces TDD (Test Driven Development) and self-healing tests.
allowed-tools: Bash, Read, Edit, Write
---

# Test Driven Agent Protocol

## 1. The Red-Green-Refactor Cycle
1.  **Red**: Write a test that fails (demonstrating the bug or missing feature).
    - *Agent Note*: If fixing a bug, YOU MUST reproduce it with a test first.
2.  **Green**: Write the minimal code to pass the test.
3.  **Refactor**: Clean up the code while ensuring tests still pass.

## 2. Test Coverage Requirements
- **Happy Path**: The "standard" usage case.
- **Sad Path**: Error states, network failures, invalid inputs.
- **Edge Cases**: Empty lists, max values, concurrent actions.

## 3. Self-Healing Mandate
If a test fails after your changes:
- **DO NOT** delete the test.
- **DO NOT** comment out the assertion.
- **DO NOT** change the test expectation to match the buggy result (unless the spec changed).
- **DO**: Fix the implementation logic until the test passes.

## 4. Integration vs Unit
- **Unit**: Mock external dependencies (Supabase, API). Fast, isolated.
- **Integration**: Test the hook or service with realistic (mocked) data flows.

## 5. Verification Checklist
- [ ] Did I write a test case for this requirement?
- [ ] Did I run `npm test <filename>`?
- [ ] Did I check specifically for regression in related headers/components?

Files in this skill

  • SKILL.md1.4 KB
  • description_cn.txt92 B
  • description_de.txt101 B
  • description_en.txt97 B
  • description_es.txt104 B
  • description_fr.txt105 B
  • description_ja.txt111 B
  • description_ko.txt113 B
  • description_tw.txt92 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.