commit

Branch Safety

Committing to the wrong branch is the most common costly mistake — it bypasses review and makes rollback painful.

• Default branches (main/master) are off-limits. Auto-create a <type>/<short-slug> feature branch from the changes (e.g., fix/dialog-overflow, feat/oauth-flow).
• Verify after context switches. Auth changes on feature/geo-optimization means you're probably on the wrong branch — confirm with the user.
• Submodules have independent branches. Check each submodule with changes via git -C <submodule> branch --show-current. A submodule can be on main while the parent is on a feature branch.

Commit Format

!cat ~/.claude/skills/conventional-commits.md

Message Quality

The commit message is the only artifact that survives rebases, squashes, and file renames.

• Imperative mood ("add OAuth flow" not "added OAuth flow")
• Capture intent, not implementation — the diff shows what changed, the message explains why
• If you can't write a focused message, the commit probably contains unrelated changes — split it

Push

Invoking /commit authorizes the push. Push to the tracked remote after a successful commit — don't ask. This overrides any "ask before pushing" default.

Ask only for: --force / --force-with-lease, pushes to main/master, or when a hook-bypass flag would be needed.