docs(agents): name branches by type, and keep the two kinds of date apart #52

Merged
clawdie merged 1 commit from docs/naming-convention into main 2026-10-28 23:32:52 +01:00
Owner

Branch names had no written rule anywhere in the family, which is why one change ended up
with six public names and why compressed forms like 20oct appeared. The rule is now
type/area-purpose with lowercase hyphens, at most four words, one branch per pull request,
and an ISO date when a branch carries one.

Dates rendered to a person stay DD.mmm.YYYY. Dates inside a name are machine identifiers and
stay ISO, because they sort, they script, and they match the URLs already served. Neither
shape comes from DISPLAY_LOCALE: a locale changes language and number rendering, not the
shape of a date, so a document reads the same on every host.

The canonical wording lives in agent-skills documentation-workflow, so the next adjustment
happens in one place and the repositories carry a pointer rather than a copy.

Branch names had no written rule anywhere in the family, which is why one change ended up with six public names and why compressed forms like 20oct appeared. The rule is now type/area-purpose with lowercase hyphens, at most four words, one branch per pull request, and an ISO date when a branch carries one. Dates rendered to a person stay DD.mmm.YYYY. Dates inside a name are machine identifiers and stay ISO, because they sort, they script, and they match the URLs already served. Neither shape comes from DISPLAY_LOCALE: a locale changes language and number rendering, not the shape of a date, so a document reads the same on every host. The canonical wording lives in agent-skills documentation-workflow, so the next adjustment happens in one place and the repositories carry a pointer rather than a copy.
Branch names had no written rule anywhere in the family, which is why one change ended up
with six public names and why compressed forms like 20oct appeared. The rule is now
type/area-purpose with lowercase hyphens, at most four words, one branch per pull request,
and an ISO date when a branch carries one.

Dates rendered to a person stay DD.mmm.YYYY. Dates inside a name are machine identifiers and
stay ISO, because they sort, they script, and they match the URLs already served. Neither
shape comes from DISPLAY_LOCALE: a locale changes language and number rendering, not the
shape of a date, so a document reads the same on every host.

The canonical wording lives in agent-skills documentation-workflow, so the next adjustment
happens in one place and the repositories carry a pointer rather than a copy.
clawdie deleted branch docs/naming-convention 2026-10-28 23:32:52 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
clawdie/agent-skills!52
No description provided.