[OCaml] Mobile-friendly clone of cgit.
docs add Conventional Branch spec to agent guidance
Add Conventional Branch v1.1.0 specification alongside the existing Conventional Commits rules in the Version control system section. Covers purpose prefixes, AI agent source prefixes, trunk branches, description format rules, and ticket number guidance.
.kiro/steering/agents.md
@@ -49,11 +49,29 @@
49
49
### Version control system
50
50
51
51
- The project SHALL use Git as its version control system.
52
Added:
53
Added:
#### Conventional Commits
54
Added:
55
Added:
- Commit messages SHALL follow the [Conventional Commits](https://www.conventionalcommits.org) specification.
56
Added:
- The commit message structure SHALL be: `<type>(<optional scope>): <description>`.
57
Added:
- Allowed types include: `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore`, `revert`.
58
Added:
- Breaking changes SHALL be indicated by a `!` after the type/scope, or by a `BREAKING CHANGE:` footer.
52
59
- Commits created by an AI agent SHALL indicate so in the commit fields:
53
60
- `user.name` — concatenate agent model name, and intelligence or reasoning level.
54
61
- `user.email` — fictitious e-mail address identifying the agent's parent company.
55
62
- A commit SHALL be created after every modification request.
56
63
- If the next request is an adjustment, additional steering, or concerns the same files as those already committed, the latest commit SHALL be amended rather than a new commit being created.
64
Added:
65
Added:
#### Conventional Branch
66
Added:
67
Added:
- Branch names SHALL follow the [Conventional Branch](https://conventional-branch.github.io/) v1.1.0 specification.
68
Added:
- The branch name structure SHALL be: `<type>/<description>`.
69
Added:
- Allowed purpose prefixes: `feature/` (or `feat/`), `bugfix/` (or `fix/`), `hotfix/`, `release/`, `chore/`.
70
Added:
- Branches created by an AI agent SHALL use the appropriate AI agent source prefix (e.g. `ai/`, `claude/`, `copilot/`, `cursor/`, `codex/`).
71
Added:
- Trunk branches (`main`, `master`, `develop`) do not use a prefix.
72
Added:
- Branch descriptions SHALL use lowercase alphanumerics and hyphens only (dots permitted in release versions).
73
Added:
- Consecutive, leading, or trailing hyphens or dots MUST NOT appear in descriptions.
74
Added:
- Ticket numbers SHOULD be included where applicable (e.g. `feat/issue-42-add-pagination`).
57
75
58
76
## Documentation
59
77