Push What You Did

4. Run pre-checks in parallel

• Run in parallel inside each affected repository: git status, git diff, git log --oneline -5
• Summarize the repository state before staging
• If the branch is both ahead and behind, the worktree is clean, and there are no owned pending paths, treat it as sync-only: run git pull --rebase and then git push

5. Verify owned paths before staging

• Check each owned path with git status --short -- <path> or equivalent
• Drop paths that no longer have changes
• If no owned paths remain after verification, do not create an empty commit

6. Stage only owned paths

• Never use git add -A, git commit -a, or any equivalent all-files shortcut
• Stage only the verified owned paths
• Use path-scoped staging that handles creates, edits, and deletions correctly
• Keep quoting safe for spaces and special characters in file names

7. Commit from the staged diff

• Write the commit message with HEREDOC
• Base the summary on git diff --cached
• Describe only the staged changes, not the full dirty worktree
• Never include signature lines or co-author trailers unless the user explicitly asks
• Do not create empty commits

8. Handle hook rewrites carefully

• If pre-commit hooks modify files, inspect which paths changed
• If hook changes stay entirely within the owned path list, re-stage only those owned paths and retry the commit
• If hooks modify files outside the owned path list, stop and ask the user instead of absorbing unrelated files into the commit

9. Push after successful commit

• Push only after the scoped commit succeeds
• If no upstream is configured, push with -u origin <current-branch>
• If push fails because the remote moved ahead, prefer git pull --rebase and retry
• If push still fails, treat it as an exceptional condition and ask the user

Hard Rules

• Never update git config
• Never run interactive git commands
• Never silently expand the owned path list to make the commit succeed
• Never commit unrelated untracked files just because they are present
• Never convert this scoped workflow into the all-files behavior of Commit&Push

Practical Staging Pattern

• For existing or new files, prefer path-scoped git add -- <paths>
• For deleted or renamed tracked paths, use path-scoped update staging as needed so removals are captured without staging unrelated files
• Recompute the final staged diff with git diff --cached --stat before committing

Trigger Examples

• push what you did
• 只提交并推送你这次改的文件
• 不要碰别人的改动，把你做的提交上去
• commit only your changes and push