Git Conventions

Branches

• JIRA-linked: <jira-key>/<descriptive-slug> (e.g. ag-12345/fix-tooltip-flicker)
• No JIRA: <initials>/<descriptive-slug> (e.g. at/improve-watch-reload-time)
• Release: b12.0.0 (see releases skill)
• Slugs use kebab-case. JIRA key casing is flexible (both ag-12345 and AG-12345 are used).
• Multiple tickets: join with underscore before the slug (e.g. CRT-1030_CRT-1044/fix-highlight)

Commits

• First line: AG-XXXX <description> (uppercase JIRA key, imperative mood). A colon after the key is also acceptable: AG-XXXX: <description>.
• No JIRA: <description> (imperative mood)
• Keep the first line under 72 characters.
• Multi-line: blank line after the first line, then body paragraphs or bullet points for additional context.
• Never attribute agentic tooling (no "Co-authored-by", "Generated by", or similar).

Pull Requests

• Base branch: latest (the default branch — not main or master). Use a bX.Y.Z release branch as base only when the work targets that release.
• Title: AG-XXXX <description> for JIRA-linked; plain description otherwise. Under 70 characters.
• Multiple tickets: comma-separate keys (e.g. CRT-1030, CRT-1044 Fix highlight)
• Body (JIRA-linked): JIRA ticket link(s). Add context only when the change needs explanation beyond the ticket.
• Body (no JIRA): concise description of the change.
• Keep descriptions concise — this is a public repo.
• Never attribute agentic tooling.