What I do
- •Route commit-related work to
@gitterwith enough context to produce meaningful commit groups. - •Enforce a clean-ending workflow: identify remaining dirty files, decide include/skip, and end with a verified
git status. - •Encourage a map-reduce style for large diffs: one global diff summary first, then scoped commit units.
When to use me
Use this whenever:
- •The user asks for commits or cleanup of working tree changes.
- •The repo has multiple unrelated changes that should be grouped.
- •You need a clear final report (commits made, skipped files, final status).
Default orchestration pattern
- •Global pass: ask
@gitterfor a single "giant diff" summary and proposed commit buckets. - •Scoped commit passes: execute each bucket as a separate commit unit.
- •Finalization pass: verify
git status --shortis clean and explain any intentional leftovers.
Important:
- •Do not run multiple commit writers in parallel on the same repository.
- •Parallel commit execution is only safe when each worker has an isolated repo/worktree.
Handoff template
Send @gitter context like:
- •Goal: <what the user asked for>
- •Scope: <files/areas touched>
- •Strategy: <global summary only | scoped commit unit>
- •Unit boundary: <exact files or path globs for this commit>
- •Clean-state requirement: <must end clean / list approved leftovers>
- •Notes: <tests run, message style, constraints>
Return contract for @gitter
Expect:
- •Commit plan or executed commit list (hash + title + files)
- •Skipped files with reason
- •Final
git status --shortsummary