planning-with-files
83Organize Long AI Tasks with Planning Files
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.
Apply Test-Driven Development
Teams often ship changes without proof that tests catch the intended behavior. This skill guides Claude, Codex, and Claude Code through strict red, green, refactor steps.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "test-driven-development" from https://skillstore.io/skills/zhanlincui-test-driven-development.md and its manifest at https://skillstore.io/api/skills/zhanlincui-test-driven-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "test-driven-development". Add retry behavior for failed operations.
Expected outcome:
The agent starts with one failing retry test, verifies the failure, adds minimal retry logic, and confirms the test passes.
Using "test-driven-development". Fix empty email validation.
Expected outcome:
The agent writes a failing validation test, implements the smallest validation change, and keeps the full test suite passing.
Using "test-driven-development". Review tests that use many mocks.
Expected outcome:
The agent flags assertions about mock existence and recommends tests that verify user-visible or domain behavior.
The static external-command and reconnaissance findings are false positives caused by markdown fences, examples, and ordinary testing language. I found one semantic risk: the skill encourages deleting implementation code when TDD was not followed, which can cause unwanted data loss without user confirmation.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/zhanlincui-test-driven-development/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zhanlincui-test-driven-development?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/zhanlincui-test-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zhanlincui-test-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/zhanlincui-test-driven-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>ZhanlinCui. (2026). test-driven-development security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zhanlincui-test-driven-development/audits/5@techreport{zhanlincui-zhanlincui-test-driven-development-2026,
author = {ZhanlinCui},
title = {test-driven-development security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/zhanlincui-test-driven-development/audits/5},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-driven-development security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "ZhanlinCui"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/zhanlincui-test-driven-development/audits/5"
identifiers:
- type: other
value: "skillstore:zhanlincui-test-driven-development:audit:5"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
dmjgilbert-test-driven-development
2026-09-09
obra-test-driven-development
2026-09-09
cycleaddict-test-driven-development
2026-09-09
cygnusfear-test-driven-development
2026-09-09
addyosmani-test-driven-development
2026-09-22
dyai2025-test-driven-development
2026-09-09
codingcossack-test-driven-development
2026-09-09
zhanlincui-test-driven-development
2026-09-09
sickn33-test-driven-development
2026-09-09
davila7-test-driven-development
2026-09-09
Use the skill to define the expected behavior as a failing test before adding production code.
Reproduce the bug with a failing test, then implement the smallest change that makes it pass.
Use the checklist and anti-pattern guidance to review whether tests cover real behavior.
Use test-driven development for this change. First write one failing test for the expected behavior, then implement the minimum code.
Reproduce this bug with a failing test before changing production code. Show why the test fails, then make it pass.
Use existing tests or add missing characterization tests first. Refactor only after tests prove the current behavior is covered.
Review these tests with the TDD and anti-pattern guidance. Identify tests that verify mocks instead of real behavior.
Author
ZhanlinCuiLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/test-driven-developmentRef
88a205c7f635a966e31156313b590d59007c5caa
Maintenance freshness
7/18/2026
Usage
97 downloads ยท 182 views
File structure
๐ SKILL.md
Organize Long AI Tasks with Planning Files
Long AI sessions can lose goals, decisions, and progress. This skill guides Claude, Codex, and Claude Code to store plans, findings, and logs in project files.
Generate Bilingual GitHub Release READMEs
Release notes and README updates can take time before each GitHub release. This skill generates bilingual release documentation and guides review, commit, and push steps.
Organize Obsidian Notes with AI
Obsidian vaults can become hard to review and update consistently. This skill helps Claude and Codex create daily notes, capture ideas, and summarize recent work.
Process PDFs with Extraction and Form Tools
PDF work often requires separate tools for text, tables, pages, and forms. This skill gives Claude, Codex, and Claude Code guided workflows and helper scripts for PDF tasks.
Build Distinctive Frontend Interfaces
Generic web interfaces can feel unfinished and forgettable. This skill guides Claude, Codex, and Claude Code toward polished frontend work with clear visual direction.
Plan Creative Work Before Building
Teams often start implementation before goals, constraints, and trade-offs are clear. This skill guides Claude, Codex, and Claude Code through structured brainstorming before design work begins.
Apply Test-Driven Development
by sickn33
Unstructured coding often produces unverified behavior and costly rework. This skill guides development through focused failing tests, minimal implementations, and disciplined refactoring.
Analyze Patterns Across Your Codebase
by C0ntr0lledCha0s
Large codebases hide repeated structures and inconsistent decisions. This skill maps design patterns, architecture, conventions, duplication, and anti-patterns with evidence and recommendations.
Refactor Code Safely
by supercent-io
Complex code slows changes and raises regression risk. This skill guides behavior-preserving refactors with tests, extraction patterns, and validation steps.
Search Code by AST Structure
by 0xDarkMatter
Text searches miss semantic relationships and produce noisy matches. This skill uses ast-grep patterns to locate code structures and prepare focused refactors.
Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Find Code Context Faster
by 89jobrien
Developers often lose time tracing why code exists and what depends on it. This skill prompts Claude, Codex, or Claude Code to gather related graph knowledge, callers, imports, and tests before changes.