mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-13 21:33:32 +08:00
Merge pull request #278 from pangerlkr/feat/separate-development-workflow-235
feat(rules): separate Feature Implementation Workflow from git-workflow.md (fixes #235)
This commit is contained in:
29
rules/common/development-workflow.md
Normal file
29
rules/common/development-workflow.md
Normal file
@@ -0,0 +1,29 @@
|
|||||||
|
# Development Workflow
|
||||||
|
|
||||||
|
> This file extends [common/git-workflow.md](./git-workflow.md) with the full feature development process that happens before git operations.
|
||||||
|
|
||||||
|
The Feature Implementation Workflow describes the development pipeline: planning, TDD, code review, and then committing to git.
|
||||||
|
|
||||||
|
## Feature Implementation Workflow
|
||||||
|
|
||||||
|
1. **Plan First**
|
||||||
|
- Use **planner** agent to create implementation plan
|
||||||
|
- Identify dependencies and risks
|
||||||
|
- Break down into phases
|
||||||
|
|
||||||
|
2. **TDD Approach**
|
||||||
|
- Use **tdd-guide** agent
|
||||||
|
- Write tests first (RED)
|
||||||
|
- Implement to pass tests (GREEN)
|
||||||
|
- Refactor (IMPROVE)
|
||||||
|
- Verify 80%+ coverage
|
||||||
|
|
||||||
|
3. **Code Review**
|
||||||
|
- Use **code-reviewer** agent immediately after writing code
|
||||||
|
- Address CRITICAL and HIGH issues
|
||||||
|
- Fix MEDIUM issues when possible
|
||||||
|
|
||||||
|
4. **Commit & Push**
|
||||||
|
- Detailed commit messages
|
||||||
|
- Follow conventional commits format
|
||||||
|
- See [git-workflow.md](./git-workflow.md) for commit message format and PR process
|
||||||
@@ -1,7 +1,6 @@
|
|||||||
# Git Workflow
|
# Git Workflow
|
||||||
|
|
||||||
## Commit Message Format
|
## Commit Message Format
|
||||||
|
|
||||||
```
|
```
|
||||||
<type>: <description>
|
<type>: <description>
|
||||||
|
|
||||||
@@ -21,25 +20,5 @@ When creating PRs:
|
|||||||
4. Include test plan with TODOs
|
4. Include test plan with TODOs
|
||||||
5. Push with `-u` flag if new branch
|
5. Push with `-u` flag if new branch
|
||||||
|
|
||||||
## Feature Implementation Workflow
|
> For the full development process (planning, TDD, code review) before git operations,
|
||||||
|
> see [development-workflow.md](./development-workflow.md).
|
||||||
1. **Plan First**
|
|
||||||
- Use **planner** agent to create implementation plan
|
|
||||||
- Identify dependencies and risks
|
|
||||||
- Break down into phases
|
|
||||||
|
|
||||||
2. **TDD Approach**
|
|
||||||
- Use **tdd-guide** agent
|
|
||||||
- Write tests first (RED)
|
|
||||||
- Implement to pass tests (GREEN)
|
|
||||||
- Refactor (IMPROVE)
|
|
||||||
- Verify 80%+ coverage
|
|
||||||
|
|
||||||
3. **Code Review**
|
|
||||||
- Use **code-reviewer** agent immediately after writing code
|
|
||||||
- Address CRITICAL and HIGH issues
|
|
||||||
- Fix MEDIUM issues when possible
|
|
||||||
|
|
||||||
4. **Commit & Push**
|
|
||||||
- Detailed commit messages
|
|
||||||
- Follow conventional commits format
|
|
||||||
|
|||||||
Reference in New Issue
Block a user