메뉴
Guide Test-Driven Development workflow with Red-Green-Refactor cycle. Use when developing features, fixing bugs, or when user mentions TDD/テスト駆動開発/test-first.
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 | Practicing TDD |
| description | Guide Test-Driven Development workflow with Red-Green-Refactor cycle. Use when developing features, fixing bugs, or when user mentions TDD/テスト駆動開発/test-first. |
| allowed-tools | Read, Write, Edit, Bash |
テスト駆動開発（TDD）のベストプラクティスに従った開発フローを管理するスキル。
1. Red → テストを書いて失敗させる
2. Green → テストを通す最小限のコード
3. Refactor → コードを整理整頓
4. 繰り返し
やるべきことを箇条書きで整理（テストリスト）
src/__tests__/ または実装ファイルと同階層の *.test.ts(x) に配置pnpm test で必ず全スイートを実行テスト追加・変更後は必ず実行：
pnpm run lint && pnpm run typecheck
詳細は references.md を参照。