agentleFS
Sign inStart free
KbWenKbWen/agent-virtual-office/.agents/skills/test-driven-development/SKILL.md

test-driven-development

Skill65 starsChanged 3 months agoMITView on GitHub

Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 4

    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:

    Red: Write a failing test describing the expected behavior.

    line 20
  2. Distinctive:

    Green: Write the minimal code to make the test pass.

    line 21
  3. Distinctive:

    Do NOT write massive amounts of features before writing tests.

    line 27
  4. Distinctive:

    All tests MUST pass after refactoring.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 178 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

Test-Driven Development

Overview

TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.

When to Use

  • Adding or modifying core logic.
  • Fixing bugs and needing regression protection.
  • Requirements can be written as explicit input/output acceptance tests.

Workflow

  1. Red: Write a failing test describing the expected behavior.
  2. Green: Write the minimal code to make the test pass.
  3. Refactor: Clean up naming, structure, and duplication.
  4. Repeat the cycle until acceptance criteria are met.

Ironclad Rules

  • Do NOT write massive amounts of features before writing tests.
  • Focus on one small goal per cycle.
  • All tests MUST pass after refactoring.

Download now (ZIP)

  • Other versions190 projects use a version of this.

    Word for word · 1

    1. KbWen/agentic-os★ 224100% same

    Edited · 0

    None found.

    Wrote their own version · 189

    1. obra/superpowers★ 305ksame name
    2. NousResearch/hermes-agent★ 259ksame name
    3. addyosmani/agent-skills★ 112ksame name
    4. cloudflare/computer★ 9.8ksame name
    5. jnMetaCode/superpowers-zh★ 8.4ksame name
    6. openai/plugins★ 7.4ksame name
    7. farm-fe/farm★ 5.6ksame name
    8. microsoft/FluidFramework★ 5ksame name
    9. mikeyobrien/ralph-orchestrator★ 3.2ksame name
    10. crbnos/carbon★ 2.8ksame name

    179 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use chinese-code-review, chinese-commit-conventions 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.
    • GEd520Skill

      chinese-code-review

      中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。

      Also in 7 projects that use this

    • GEd520Skill

      chinese-commit-conventions

      中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。

      Also in 7 projects that use this

    • obraSkill

      diagnosing-superpowers

      Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

      Also in 12 projects that use this

    • LLl0k0laDSkill

      git-workflow-and-versioning

      Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

      Also in 44 projects that use this

    • LLl0k0laDSkill

      using-agent-skills

      Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

      Also in 36 projects that use this

    • 10CGSkill

      workflow-runner

      十步循环轻量编排器，协调 Phase Skills 执行，支持灵活组合。

      Also in 8 projects that use this

    • +2 more from GEd520
    • +3 more from LLl0k0laD
  • In this repository16 other files it gives its agents.

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