ABOUTME: Git conventional commit format and version control best practices

ABOUTME: Commit message standards, branch strategies, workflow patterns

Source Control

Quick Reference

git commit -m "feat: add user authentication"
git checkout -b feat/user-auth
git fetch origin && git rebase origin/main
git stash && git stash pop

Conventional Commits

Format: <type>(<scope>): <subject> (scope/body/footer optional), standard Conventional Commits types.

Rules: Imperative mood, present tense, lowercase, no period, max 50 chars

# Good
git commit -m "feat(auth): add JWT validation"
git commit -m "fix: resolve race condition"

# Bad
git commit -m "Fixed stuff"      # Not conventional
git commit -m "Feat: Add thing"  # Capital letter

Commit Process

1. Check state:

   git status && git diff HEAD && git branch --show-current && git log --oneline -5

2. Verify NOT on main/master (abort if so, unless authorized)
3. Stage specific files (never git add -A):

   git add <specific-files>

4. Commit with conventional format:

   git commit -m "<type>(<scope>): <subject>"

Branch Naming

Workflow

Post-PR Loop (babysitting)

After a PR is opened, CI failures and review comments arrive asynchronously. Instead of Max polling, offer a time-based loop:

/loop 10m check PR #<N>: if CI failed, diagnose and fix; if new review comments, address them; commit fixes on the PR branch and push; stop when CI is green and no comments are unaddressed

Rules for the loop:

• Push scope: the loop pushes fixes to the PR branch only; merging the PR stays with Max, even when CI is green and every comment is addressed.
• Never force-push inside a loop; --force-with-lease only, and only for rebase-on-main conflicts Max asked for.
• Commits inside the loop follow the same conventional format and pre-commit gate (make check && make test-e2e); hooks are never bypassed under loop time pressure.
• Match the interval to the external system: CI that takes ~10 minutes doesn't need a 2-minute loop.
• Stop condition is part of the prompt (CI green + comments addressed); the loop must not idle-run after the PR merges: cancel it from the session that started it (interrupt, or ask the loop to stop).

Rules

• Commit, push the feature branch and open the PR without asking; never merge a PR (no gh pr merge, no auto-merge, no local merge into the integration branch or main): the merge is Max's review gate
• NEVER work on main/master unless explicitly authorized
• Small, logical commits; no huge unrelated changes
• --force-with-lease, never bare --force on shared branches
• Run make check && make test-e2e before committing (see language skills for the expansion)
• Conflict resolution and recovery commands (reset, reflog, revert, amend): use standard git, no project-specific conventions here.