菜单
Guide Test-Driven Development with task splitting, Red-Green-Refactor cycle, and framework auto-detection. Use when developing features with TDD approach, fixing bugs test-first, or when user mentions "TDD", "テスト駆動開発", "test-first", "/tdd".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run external Ralph Loop (Geoffrey Huntley method) with clean context per iteration. Supports Simple mode (single PROMPT.md) and Full Ecosystem mode (specs/, fix_plan.md, AGENT.md, plan/build prompts). Unlike the official ralph-loop plugin which uses Stop hooks (same session, context pollution), this spawns fresh `claude -p` sessions each iteration. Use when user mentions "camone-ralph-loop", "external ralph", "clean ralph loop", "外部ラルフ", "ラルフループ実行", or wants to run iterative AI development with isolated context windows.
Execute semantic git commits with individual file staging, prefix selection, and split-commit enforcement. Use when committing code, managing git history, or when user mentions git/commit/push.
Detect project tech stack and generate a comprehensive, production-grade .gitignore. Covers 15+ languages, 20+ frameworks, security patterns, modern tooling, and monorepo support.
Install MCP servers into the current project scope using claude mcp add. Use when setting up a new project, when user mentions MCP setup, project MCP, MCPインストール, MCPセットアップ, or /installing-project-mcps.
Create a git worktree via gtr (git-worktree-runner) for a GitHub issue and generate a CLAUDE.local.md with issue context so that Claude Code launched in that worktree knows what to work on. Issue-specific context is written to CLAUDE.local.md (not .claude/CLAUDE.md) to avoid Git conflicts when merging PRs from multiple worktrees. Use when user mentions "gtr issue", "issue worktree", "issueでworktree", "issueに着手", "gtr-issue", or wants to set up an isolated worktree for a specific GitHub issue. Requires: gtr (git-worktree-runner) and gh CLI installed.
Generate detailed, agent-executable feature specifications by interviewing the user with AskUserQuestionTool. Transforms rough ideas into comprehensive SPEC.md files through phased deep interviews (5 phases) covering technical architecture, data design, API design, UI/UX, edge cases, security, performance, and tradeoffs. Produces hybrid specs with Acceptance Criteria and phased implementation tasks with dependencies. Use when user mentions "spec", "仕様書作成", "仕様駆動", "インタビューして", "SPEC.md", "feature spec", "仕様を書いて", "大きな機能を計画", or wants to plan a feature before implementation.
| name | guiding-tdd-development |
| description | Guide Test-Driven Development with task splitting, Red-Green-Refactor cycle, and framework auto-detection. Use when developing features with TDD approach, fixing bugs test-first, or when user mentions "TDD", "テスト駆動開発", "test-first", "/tdd". |
機能をTDD可能な小さな単位に分割し、Red-Green-Refactorサイクルで実装するスキル。
1. 要件分析 → タスク分割（ToDoリスト）
2. 各タスクで TDD サイクル:
RED → GREEN → REFACTOR → ToDoリスト更新 → 繰り返し
## TDDタスク分割
### 実装する機能
<機能の概要>
### タスク一覧
1. [単体機能A] のテストと実装
2. [単体機能B] のテストと実装
3. [統合機能C] のテストと実装
### タスク: [タスク名]
#### RED: テストを書く
<失敗するテストコード>
#### GREEN: 実装する
<テストを通す最小実装>
#### REFACTOR: リファクタリング
<改善されたコード>
バグ修正もTDDで行う:
プロジェクトの設定ファイルからテストフレームワークを自動検出する:
テストファイルの配置場所もプロジェクトの慣習に従う。
詳細は references/tdd-resources.md を参照。