auto-commit

Auto Commit

Automatically analyze git working tree, group changes into logical batches, commit each batch with a concise message, and push to remote. No Co-Authored-By or any AI attribution is added.

When to Use

• User says "auto commit", "batch commit", "commit and push", "提交代码", "自动提交"
• User triggers /auto-commit

Workflow

Step 1: Analyze Git Status

Run these commands in parallel to understand the current state:

git status --short
git diff --stat
git diff --cached --stat
git log --oneline -5
git branch --show-current

Step 2: Identify Logical Groups

Analyze all changed files (staged + unstaged + untracked) and group them by logical concern. Common grouping strategies:

1. By module/feature: Files that belong to the same feature or module go together
2. By type of change: Schema changes, service changes, UI changes, config changes, etc.
3. By dependency: If file A depends on changes in file B, they should be in the same commit

Typical groups (adapt based on actual changes):

• convex/schemas/ changes → schema/type commits
• convex/repositories/ + convex/services/ → backend logic commits
• convex/*.ts (functions layer) → API layer commits
• src/components/ → UI component commits
• src/routes/ → route/page commits
• Config files (package.json, tsconfig.json, vite.config.ts, etc.) → config commits
• Test files → test commits
• Migration files → migration commits

Step 3: Exclude Other People's Changes

CRITICAL: Before committing, check git status carefully:

• Only commit files that are part of the current user's work
• If there are files that appear to be from other people's branches or unrelated work, skip them
• Do NOT git restore or git checkout other people's files — leave them as-is
• Do NOT use git add -A or git add . — always add specific files by name

Step 4: Batch Commit

For each logical group, use && to chain the git add and git commit commands in a single Bash call, ensuring they run sequentially and stop on failure: