mirror of
https://github.com/affaan-m/ECC.git
synced 2026-11-07 16:45:53 +00:00
Kiro only loads steering files automatically in every conversation when they use `inclusion: always`; `auto` loads them only when the request matches the description. Switch the always-on steering files to `always` and update README, install.sh and docs accordingly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
31 lines
947 B
Markdown
31 lines
947 B
Markdown
---
|
|
inclusion: always
|
|
name: git-workflow
|
|
description: Git workflow guidelines for conventional commits and pull request process
|
|
---
|
|
|
|
# Git Workflow
|
|
|
|
## Commit Message Format
|
|
```
|
|
<type>: <description>
|
|
|
|
<optional body>
|
|
```
|
|
|
|
Types: feat, fix, refactor, docs, test, chore, perf, ci
|
|
|
|
Note: ECC-managed installs set `"includeCoAuthoredBy": false` in `~/.claude/settings.json`, so commits carry no `Co-Authored-By` trailer by default. To keep Claude attribution, set `"includeCoAuthoredBy": true` or configure `attribution`; ECC never overwrites an explicit choice.
|
|
|
|
## Pull Request Workflow
|
|
|
|
When creating PRs:
|
|
1. Analyze full commit history (not just latest commit)
|
|
2. Use `git diff [base-branch]...HEAD` to see all changes
|
|
3. Draft comprehensive PR summary
|
|
4. Include test plan with TODOs
|
|
5. Push with `-u` flag if new branch
|
|
|
|
> For the full development process (planning, TDD, code review) before git operations,
|
|
> see the development workflow rule.
|