agentleFS
Sign inStart free
bis-codebis-code/claude-toolkit/.claude/skills/tdd-workflow/SKILL.md

tdd-workflow

Skill8 starsChanged 6 months agoMITView on GitHub

Enforce test-first discipline with red-green-refactor guidance and verification checkpoints.

128 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brand-discovery, configure-ecc and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ysyecustSkill

    brand-discovery

    Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

    Also in 6 projects that use this

  • royaluniondesign-sysSkill

    configure-ecc

    Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

    Also in 12 projects that use this

  • junimnjwSkill

    ralphinho-rfc-pipeline

    RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

    Also in 12 projects that use this

  • loulanyueSkill

    nuxt4-patterns

    Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

    Also in 10 projects that use this

  • royaluniondesign-sysSkill

    content-hash-cache-pattern

    Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.

    Also in 16 projects that use this

  • RojiosSkill

    dart-flutter-patterns

    Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If arguments are provided (feature description, bug to fix, files to refactor), use those

    line 13
  2. Distinctive:

    All tests pass (no regressions)

    line 35

“Common” is measured: kept by at least 6 in 10 of the 117 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/tdd-workflow

Spawns the tdd-guide agent to enforce TDD discipline throughout an implementation task, including verification checkpoints at each step.

Steps

  1. Gather context — understand what needs TDD guidance:
    • If arguments are provided (feature description, bug to fix, files to refactor), use those
    • Otherwise, ask the user what they are implementing
    • Detect the test framework and test command from .claude-toolkit.json or auto-detection
    • Identify existing test files related to the scope
  2. Spawn the agent — use the Task tool:
    Task tool with subagent_type="tdd-guide"
    Pass in the prompt:
    • The task description (feature, bug fix, or refactor)
    • The test command and framework
    • Existing test file paths for the affected modules
    • Any relevant source files for context
  3. Present guidance — relay the agent's TDD plan:
    • Ordered list of test cases to write (red phase)
    • Minimum implementation for each test (green phase)
    • Refactoring suggestions after tests are green
    • Verification checkpoints between each cycle:
      • Type check / compile passes
      • Lint passes
      • All tests pass (no regressions)
      • Runtime verification (app starts, endpoints respond)
  4. Offer follow-up actions:
    • "Start first test?" — write the first failing test
    • "Verify checkpoint?" — run the full verification loop
    • "Review coverage?" — check what is tested and what is missing

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free