commit

Commit Current Work

Working Directories

1. Obsidian workspace (docs, plans, features): __VAULT_ROOT__
2. Codebase (all LE services): __CODEBASE_ROOT__

Process

1. Check current branch: git branch --show-current

   • If on main or master: NEVER commit directly. Analyze the diff to suggest a smart branch name:

     1. Run GIT_EDITOR=true git diff --stat to see changed files

     2. Infer type from changes:

        • New files with business logic → feat
        • Modified existing logic fixing a defect → fix
        • Only test files → test
        • Only config/CI/deps → chore
        • Only .md files → docs
        • Restructuring without behavior change → refactor
        • Performance-related changes → perf

     3. Infer scope from file paths:

        • svc-experiences/... → svc-experiences
        • www-le-customer/... → www-le-customer
        • src/checkout/... → checkout
        • Multiple services → use the primary one or the shared module name

     4. Infer description from the nature of changes (function names, file names, test names)

     5. Present to user with context:

        You are on main. Based on the diff:
        - Type: feat (new files with business logic)
        - Scope: svc-experiences (all changed files)
        - Suggestion: feat/svc-experiences-add-complementary-filter
        
        Use this branch or prefer a different name?
        

     6. Wait for the user's response before creating the branch with git checkout -b <name>

   • If no branch exists (detached HEAD): analyze the diff and suggest a branch name before committing

2. Review changed files: GIT_EDITOR=true git diff --stat

3. Check each file is related to the current work (don't commit unrelated changes)

4. Stage relevant files by name (avoid git add .)

5. Write commit message

Commit Format

<type>(<scope>): <short description>

- Bullet point 1
- Bullet point 2

Types