zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-03-30 13:43:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #278 from pangerlkr/feat/separate-development-workflow-235

Browse Source 
feat(rules): separate Feature Implementation Workflow from git-workflow.md (fixes #235)
This commit is contained in:
Affaan Mustafa
2026-02-24 09:11:32 -08:00
committed by GitHub
parent db27ba1eb2 253aecbebd
commit 5dad143f90
2 changed files with 31 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
rules/common/development-workflow.md Normal file
View 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

25
rules/common/git-workflow.md
View File

@@ -1,7 +1,6 @@
# Git Workflow
## Commit Message Format
```
<type>: <description>
@@ -21,25 +20,5 @@ When creating PRs:
4. Include test plan with TODOs
5. Push with `-u` flag if new branch
## 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
> For the full development process (planning, TDD, code review) before git operations,
> see [development-workflow.md](./development-workflow.md).