[johantor]

• The README's Maintaining section sets branch names to <type>/<issue>-<slug>: the Conventional Commits type and a three-to-five-word slug. With no issue, drop <issue>-.
• Same rule as docs(agents): name branches <type>/<issue>-<slug> crew#321 and docs(readme): mirror crew's structure and tone (v0.1.4) board#3. This repo has no AGENTS.md or CONTRIBUTING.md, so the README holds it.

CI checks only the marketplace catalog, which this PR does not change.

---

Generated by Claude Code

[Copilot]

🟢 Approved

The documentation-only change is low risk, with only a non-blocking example inconsistency remaining.

1 open issue

• Use a three-to-five-word branch naming example · New

What changed in this PR

This PR adds branch-naming guidance to the README’s Maintaining section, where this repository keeps contributor instructions.

Changes:

• Defines <type>/<issue>-<slug> using a Conventional Commits type and a three-to-five-word slug.
• Explains how to omit the issue number and asks contributors to rename generated branches before pushing.

File	Description
README.md	Documents the branch-naming convention and examples.

_{Review effort: Balanced}