Skip to content

Commit 02310d8

Browse files
dengwx2026dengwxclaude
authored
docs: add Claude Code development workflow skills to CLAUDE.md (#530)
Add recommended skills section covering planning (brainstorming, write-plan, execute-plan), TDD workflow, debugging, parallel execution, and review/completion. Co-authored-by: dengwx <dengwx@wanxideMacBook-Pro.local> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 31b8b1f commit 02310d8

File tree

1 file changed

+61
-0
lines changed

1 file changed

+61
-0
lines changed

CLAUDE.md

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -187,6 +187,67 @@ gh pr create --title "feat: add my feature" --body "fixes #123"
187187
- `ruff --fix` (lint) + `ruff format` (format)
188188
- Custom hook: prevents mixing internal (`xrl/`, `intetest/`) and external files in one commit
189189

190+
## Development Workflow with Claude Code
191+
192+
### Recommended Skills
193+
194+
在使用 Claude Code 进行开发时,建议按以下流程使用 skills:
195+
196+
#### 1. Planning — 先规划再动手
197+
198+
对于多步骤任务,使用 plan 相关 skills 确保方案清晰后再执行:
199+
200+
- **`/brainstorming`** — 任何新功能或行为变更前,先用此 skill 探索需求、明确设计
201+
- **`/writing-plans`** — 有明确需求/spec 后,用此 skill 生成分步实施计划,输出 plan 文件
202+
- **`/executing-plans`** — 拿到 plan 文件后,用此 skill 按步骤执行,带 review checkpoint
203+
204+
```
205+
需求 → /brainstorming → /writing-plans → plan.md → /executing-plans → 实现完成
206+
```
207+
208+
#### 2. TDD — 测试驱动开发
209+
210+
所有功能开发和 bugfix 必须遵循 TDD 流程:
211+
212+
- **`/test-driven-development`** — 在写实现代码之前调用,先写失败的测试,再写实现使其通过
213+
214+
```
215+
明确需求 → 写测试(RED) → 写实现(GREEN) → 重构(REFACTOR)
216+
```
217+
218+
TDD 要点:
219+
- 先写测试用例,确认测试失败(RED)
220+
- 写最少的实现代码使测试通过(GREEN)
221+
- 测试通过后再重构优化(REFACTOR)
222+
- 每个 cycle 保持小步迭代
223+
224+
#### 3. Debugging
225+
226+
- **`/systematic-debugging`** — 遇到 bug、测试失败或异常行为时使用,先诊断再修复,避免盲猜
227+
228+
#### 4. Parallel Execution
229+
230+
- **`/dispatching-parallel-agents`** — 当有 2+ 个独立任务时,并行分发给多个 agent 执行
231+
- **`/subagent-driven-development`** — 在当前 session 中并行执行 plan 中的独立步骤
232+
233+
#### 5. Review & Completion
234+
235+
- **`/verification-before-completion`** — 在声明任务完成前,必须运行验证命令确认结果
236+
- **`/requesting-code-review`** — 完成实现后,请求代码审查
237+
- **`/finishing-a-development-branch`** — 实现完成、测试通过后,决定如何集成(merge / PR / cleanup)
238+
239+
### Typical Feature Development Flow
240+
241+
```
242+
1. /brainstorming — 探索需求,明确设计方向
243+
2. /writing-plans — 生成分步实施计划
244+
3. /test-driven-development — 对每个步骤: 先写测试 → 再写实现
245+
4. /executing-plans — 按计划逐步执行,带 checkpoint
246+
5. /verification-before-completion — 运行全部测试,确认通过
247+
6. /requesting-code-review — 请求审查
248+
7. /finishing-a-development-branch — 提交 PR
249+
```
250+
190251
## Dependencies
191252

192253
Core: FastAPI, Pydantic v2, Ray 2.43.0, Redis, Docker CLI, Kubernetes client, APScheduler, OpenTelemetry, httpx.

0 commit comments

Comments
 (0)