From the author
Fix a bug by first writing a focused test that fails for the right reason, then making the smallest change that makes it pass. Use when the user asks for TDD or a regression test, when a bug has a cheap local test target, or for /ds-tdd.
Install
npx skills add aicodeking/deepseek-stack --skill ds-tdd -a claude-code
Installs to .claude/skills/ds-tdd/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- tddsickn33/agentic-awesome-skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Testing★ 49K
- ca-fixarbiterForge/codeArbiterFix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.Testing★ 149
- tdd-bug-fixrshankras/claude-code-apple-skillsFix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.Testing★ 845
- testhashgraph-online/awesome-codex-pluginsWrite or assess tests that prove behavior and would fail without the fix. Use when: writing tests, TDD, or asked whether a green test is enough.Testing★ 1.5K
- tdd-bug-reportGulajavaMinistudio/awesome-copilot-idWorkflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans enforcing the Prove-It pattern (failing regression test first) with rollback strategies.Testing★ 92
- regression-testingnahid-sparktales/agent-dispatcherTurn a fixed bug into a test that fails on the old code and passes on the new one. Assert behavior at the cheapest useful level and compare old behavior without reverting unrelated work or leaving scratch files. Use after a fix or when recurring defects lack coverage; not for a new feature's test strategy or an environmental/cosmetic failure.Testing★ 59
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in