tdd-loop
Skill from milad-ahmd/agent-skills
Install
npx skills add milad-ahmd/agent-skills --skill tdd-loop
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add milad-ahmd/agent-skills
/plugin install all-skills@milad-agent-skills
This skill is part of the plugin “all-skills”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the tdd-loop skill do?
Description from the SKILL.md in the source repository.
Questions about tdd-loop
What does the tdd-loop skill do?
Runs strict test-driven development one behaviour at a time. Picks the next smallest behaviour from the spec or task list, writes one failing test, makes the smallest change that passes it, then refactors with the tests green. A guard script records each step and refuses the usual shortcuts. It rejects a red step that fails for the wrong reason (syntax, import or compile error, missing function, no tests ran) and code written before any failing test. It also rejects a test that was edited, deleted, skipped or focused with .only to reach green. Works with pytest, unittest, Jest, Vitest, go test, cargo test, RSpec, Maven and Gradle. Use when the user asks to do TDD, work test-first, write the test first, follow red green refactor, build a feature test-driven from a spec or user story, or stop the agent from changing tests to make them pass.
How do I install tdd-loop?
In a terminal: npx skills add milad-ahmd/agent-skills --skill tdd-loop. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use tdd-loop?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is tdd-loop safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from milad-ahmd/agent-skills
Plans and executes large codebase migrations incrementally and safely, such as JavaScript→TypeScript, Jest→Vitest, Next.js Pages→App Router, Vue 2→3, React class→hooks, CommonJS→ESM, or any framework or major-version upgrade, verifying each step with build …
Converts a screenshot, mockup, or Figma export into a production-ready UI component that reuses the project's existing design system (React/Next, Vue, Svelte, React Native, Flutter, or SwiftUI with Tailwind, CSS modules, or …
Roasts a GitHub profile with humor, then gives genuinely useful advice. It analyzes public repos, stars, languages, missing descriptions and licenses, abandoned projects, lazy commit messages, and activity with a data script …
Rewrites a repository's README into a polished, star-worthy page with badges, a hero tagline, demo section, quickstart, features, usage, and contributing info.
Scans an AI agent's instruction and tool-config files (CLAUDE.md, AGENTS.md, skills, slash commands, subagents, Cursor and Cline rules, hooks, MCP server configs) for prompt injection, hidden Unicode or HTML-comment instructions, exfiltration commands …
Reviews a pull request or local branch diff like a senior engineer, covering correctness, security, performance, naming, and missing tests, and produces prioritized, actionable comments (optionally posted to GitHub).
Grills the user about a planned feature or code change before any code is written. It reads the relevant code and docs first so every question is specific to the repo, asks …
Manages an Instagram account end to end, covering profile and bio audits, content pillars, Reels, carousel and Story plans, captions with hooks and CTAs, hashtag sets, posting schedules, DM and comment reply …
Related skills in Testing & QA
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any …
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Automate browser interactions, test web pages and work with Playwright tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.