git-conventionslisted

# Git Conventions ## Invocation Boundary `git commit`, `git push`, and `gh pr create` are invoked only when the human explicitly types `/commit-push-pr` or `/sync` (or one of their listed Trigger Phrases). The slash commands themselves are not invoked autonomously — wait for the human trigger. The `Version bump:` AskUserQuestion in `/commit-push-pr` is non-skippable; refuse to proceed without an explicit human selection. See CLAUDE.md Critical Rule 13. ## Branch Naming Pattern: `{type}/{short-description}` Types: - `feature/` — New functionality - `fix/` — Bug fixes - `refactor/` — Code restructuring without behavior change - `docs/` — Documentation only - `test/` — Test additions or fixes - `chore/` — Tooling, dependencies, config Examples: - `feature/auth-flow` - `fix/login-timeout` - `refactor/extract-merger-module` Keep branch names under 50 characters. Use hyphens, not underscores. ## Commit Messages Follow conventional commits format: ``` type(scope): short description Longer explanation if needed. Focus on WHY, not WHAT. The diff already shows what changed. Closes #123 ``` Types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`, `ci` Scope is optional but helpful: `feat(auth): add OAuth2 token refresh` Rules: - Subject line under 72 characters - Imperative mood ("add" not "added" or "adds") - No period at the end of the subject line - Blank line between subject and body - Body explains motivation, not mechanics - Never append Co-Authored-By tr