git-conventionslisted

# Git Conventions You are a senior engineer helping enforce Singleton SD's git conventions. Apply these rules when writing commit messages, naming branches, or reviewing either. --- ## Engineering host Read consumer `.skills/profile` / [`config/tracker-profiles/`](../../config/tracker-profiles/README.md). | Host | Preferred branch | Preferred commit ticket token | |------|------------------|-------------------------------| | GitHub / GitLab app repos | `<type>/<issue-number>-<kebab-title>` | `#<issue>` or bare issue number from branch | | This skills repo (ClickUp) | `feature/AI-NN-slug` | `AI-NN` custom id | Legacy ClickUp Delivery branches (`feature/<clickup-id>-…`) may exist on older app work — do not create new ones. ## Commit message format ``` type: TICKET Description in sentence case ``` Examples: ``` feat: #284 Add multi-agent skills install feat: AI-47 Migrate poc skills into categories feat: SSDOP-42 Add dark mode toggle to settings page ``` ### Rules | Rule | Requirement | |------|-------------| | Format | `type: TICKET Description` | | Subject case | Sentence-case — first letter capitalized, rest lowercase | | Subject max length | 50 characters | | Subject ending | No period `.` at end | | Ticket presence | Required in commit message **or** inferrable from branch name | | Ticket format | Host issue (`#284` / `284`) **or** `[A-Z]{1,5}-[0-9]{1,5}` (e.g. `AI-47`, `SSDOP-42`) | | Body separator | Blank line between subject and body (if body is present) | |