Commit-Artisan: Atomic & Bisectable Git Commits

Organize only the authorized changes into logically isolated, bisectable commits. Follow current user and project git instructions, and preserve other sessions' work.

Constraints

1. Explicit paths only: Never run git add -A, git add ., git commit -a. Stage explicit file paths only.
2. Follow repository conventions: Use required message formats and trailers; do not invent attribution.
3. Keep commits independently valid: Check affected behavior and project-required gates so commits remain useful for bisecting. Reuse still-current evidence and distinguish pre-existing failures.

Commit Decomposition

Split by logical change, not by layer. Each commit holds one change a reviewer can understand alone, together with its tests and docs, so git show proves what it claims. When a feature needs several commits, order them so dependencies land first (a schema and its migration before the code that reads it), and each commit still builds and passes its tests.

Conventional Format

Use the repository's convention when it differs; otherwise: