chunk-and-commit

name	chunk-and-commit
description	Split uncommitted work into logical git commits, present each proposed commit (message plus file chunk) for confirmation, then commit only after the user approves. Use when the user asks to commit, chunk commits, split commits by article/feature/file, or commit all changes in groups.

Chunk and commit

Inspect the working tree, group changes into reviewable commits, show the plan, wait for yes, then commit. Do not run git commit until the user confirms the proposed list.

Honor grouping the user already named in this turn (e.g. "telegram and smartd together"). Do not invent extra commits for formatting-only noise.

When to use

• "commit all changes" / "chunk them" / "split into commits"
• "commit by article" / "by feature" / "logical commits"
• any commit request where the diff is more than one coherent unit

Workflow

git status + git diff (+ cached) + git log (in parallel)
        ↓
group files into commits (linked work stays together)
        ↓
draft the proposal (message + file list per commit) — stop
        ↓
user confirms / edits grouping or messages
        ↓
stage each chunk and commit in order
        ↓
git status to verify

1. Inspect

Run in parallel:

• git status
• git diff and git diff --cached
• git log (recent messages, so new ones match this repo)

Do not update git config. Do not skip hooks. Do not push unless asked.

2. Group

One commit = one reason a reviewer would want those files together.

• Feature / article / bug: the primary files plus assets they need
• Linked work: keep together when one change is useless or broken without the other (shared helper + first consumer, related posts, component + mdsvex export)