TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
A skill your agent uses when implementing any feature or bugfix, before writing implementation code.
Install Test Driven Development
$ npx skills add peintune/runjam --skill test-driven-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install peintune/runjam test-driven-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .claude/skills/test-driven-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .claude/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add peintune/runjam --skill test-driven-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install peintune/runjam test-driven-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .agents/skills/test-driven-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .agents/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peintune/runjam --skill test-driven-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install peintune/runjam test-driven-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .cursor/skills/test-driven-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .cursor/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/peintune/runjam.git --path src-tauri/builtin-skills/test-driven-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add peintune/runjam --skill test-driven-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install peintune/runjam test-driven-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .gemini/skills/test-driven-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .gemini/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install peintune/runjam test-driven-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add peintune/runjam --skill test-driven-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .github/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .github/skills/test-driven-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .github/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add peintune/runjam --skill test-driven-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install peintune/runjam test-driven-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/peintune/runjam.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src-tauri/builtin-skills/test-driven-development .opencode/skills/test-driven-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-driven-development" agent skill from https://github.com/peintune/runjam/tree/main/src-tauri/builtin-skills/test-driven-development into .opencode/skills/test-driven-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-driven-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-driven-development- GitHub stars
- 228
- Token cost
- ~234 tokens
- SKILL.md length
- 108 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing any feature or bugfix, before writing implementation code.
- Works in 3 steps: Red: Write a failing test → Green: Write minimal code to pass → Refactor: Clean up while keeping tests…
- Implementing any feature
- SKILL.md covers Rule, When to Use, Process and Anti-Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Driven Development is an agent skill from peintune/runjam. Use when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
Its SKILL.md is about 230 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test-driven development. The repository describes itself as: One desktop for all your AI coding Agent — Claude Code, Codex CLI & Gemini CLI. Auto-detect, one-click install, unified chat, file explorer, terminal & editor. Local-first. Built… The licence is MIT.
When your agent uses it
- Implementing any feature
- Before writing implementation code
Example prompts
- “/test-driven-development”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Red: Write a failing test
- Green: Write minimal code to pass
- Refactor: Clean up while keeping tests green
What it can do on your machine
Read from SKILL.md and the folder at commit b186c61. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Driven Development loads about 234 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 108 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from peintune/runjam at commit b186c61, republished under its MIT licence (© peintune). 108 words, ~234 tokens.
Download SKILL.mdSave it as
.claude/skills/test-driven-development/SKILL.md (or your agent's skills folder).- name
- test-driven-development
- description
- Use when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
Test-Driven Development (TDD)
Rule
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
When to Use
Always for:
- New features
- Bug fixes
- Refactoring with behavior changes
Skip only for:
- Config file changes
- Documentation updates
- Non-functional changes (formatting, comments)
Process
- Red: Write a failing test
- Green: Write minimal code to pass
- Refactor: Clean up while keeping tests green
Anti-Patterns
- Writing implementation before the test
- Skipping the "watch it fail" step
- Writing tests that are too coupled to implementation
- Testing framework behavior instead of your code
© peintune, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src-tauri/builtin-skills/test-driven-development of peintune/runjam.
Open the folder on GitHubat commit b186c61
Compare with similar skills
Test Driven Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Driven Development this skillpeintune/runjam | 228 | — | ~234 | Automated safety check: Pass | MIT | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT | |
| Test Driven Developmentfarm-fe/farm | 5.6k | 51 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Tapd Story PipelineTencentBlueKing/bk-bcs | 840 | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Test Driven Development
farm-fe/farm
A skill your agent uses when implementing any feature or bugfix, before writing implementation code
Tapd Story Pipeline
TencentBlueKing/bk-bcs
单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。
Absolute Init
maddhruv/absolute
One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…
More from peintune/runjam
Mermaid
peintune/runjam
Render Mermaid diagrams as SVG or ASCII art using beautiful-mermaid.
Finishing A Development Branch
peintune/runjam
A skill your agent uses when development work is complete and you need to prepare for merge.
Ppt Generation
peintune/runjam
A skill your agent uses when the user requests to generate, create, or make presentations (PPT/PPTX).
Runjam Defaults
peintune/runjam
Default constraints for every RunJam session. An agent skill from peintune/runjam.
Code Review
peintune/runjam
A skill your agent uses when reviewing code for bugs, security issues, performance problems, or adherence to best practices.
Writing Plans
peintune/runjam
A skill your agent uses for complex multi-step tasks. An agent skill from peintune/runjam.
Related
Categories
Questions about Test Driven Development
What does Test Driven Development do?
A skill your agent uses when implementing any feature or bugfix, before writing implementation code. Test Driven Development is an agent skill from peintune/runjam. Use when implementing any feature or bugfix, before writing implementation code.
When should I use Test Driven Development?
Test Driven Development fits situations like: implementing any feature; before writing implementation code.
How do I install Test Driven Development in Claude Code?
Run `npx skills add peintune/runjam --skill test-driven-development -a claude-code`. Or copy the skill folder (src-tauri/builtin-skills/test-driven-development in peintune/runjam) into .claude/skills/test-driven-development in your project. Claude Code loads it when a task matches its description.
How do I install Test Driven Development in Codex?
Run `npx skills add peintune/runjam --skill test-driven-development -a codex`. Or copy the skill folder (src-tauri/builtin-skills/test-driven-development in peintune/runjam) into .agents/skills/test-driven-development in your project. Codex loads it when a task matches its description.
Can I use Test Driven Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add peintune/runjam --skill test-driven-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-driven-development, .gemini/skills/test-driven-development, .github/skills/test-driven-development and .opencode/skills/test-driven-development in your project.
What does Test Driven Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Driven Development is instructions for the agent only.
Does Test Driven Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Driven Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Driven Development use?
Test Driven Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Driven Development use?
About 234 tokens (SKILL.md is roughly 936 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Driven Development?
Skills that share tags, products or a category with Test Driven Development: TDD (pietheinstrengholt/rssmonster, 564 stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars) and Test Driven Development (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Driven Development?
peintune (a GitHub user) maintains it in peintune/runjam, which has 228 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.
Source: peintune/runjam on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.