Context
The current AGENTS.md contains a section on conventional commits but lacks a broader description of the development workflow. It should be improved to document the full development process.
What to do
Replace/expand the conventional commit section in AGENTS.md with a more comprehensive development workflow guide covering:
Two development modes
-
Direct development on develop (default branch)
- When to use: small changes, chores, quick fixes
- Workflow: commit directly on
develop, push, CI runs, merge to main when ready
-
Feature branch from issue
- When to use: work tracked as a GitHub issue
- Branch naming convention (TBD — e.g.
feat/123-short-description, fix/123-short-description)
- Workflow: create branch from
develop, implement, PR back to develop
- How the branch relates to the issue (linking, closing keywords)
Topics to reflect on and define
- Branch naming convention for feature branches
- PR merge strategy (squash? merge commit? rebase?)
- How conventional commits map to the release pipeline (
release-it + conventional changelog)
- Whether
develop -> main merge has specific rules or cadence
This is a planning/reflection item — the exact workflow details need to be decided before documenting.
Context
The current
AGENTS.mdcontains a section on conventional commits but lacks a broader description of the development workflow. It should be improved to document the full development process.What to do
Replace/expand the conventional commit section in
AGENTS.mdwith a more comprehensive development workflow guide covering:Two development modes
Direct development on
develop(default branch)develop, push, CI runs, merge tomainwhen readyFeature branch from issue
feat/123-short-description,fix/123-short-description)develop, implement, PR back todevelopTopics to reflect on and define
release-it+ conventional changelog)develop->mainmerge has specific rules or cadenceThis is a planning/reflection item — the exact workflow details need to be decided before documenting.