stage-related-files

To group related files into logical git commits, review your changes with git status, identify related edits by feature or task, and stage each group separately using git add before committing to improve history clarity.

The best way to split mixed changes into separate git commits is to decide when to batch or split changes based on grouping criteria, then stage and commit each feature or fix independently to improve traceability and auditability.

To exclude research notes and documentation from git staging, apply grouping criteria that identify non-essential files and prevent them from being staged, ensuring only relevant code changes are included in your commits.

Yes, you can use this workflow to improve code review quality by grouping edits by feature or task, proposing commit-scopes, and following a step-by-step process to review, group, and stage files per-commit.

You should split commits for separate features in version control when changes span multiple tasks or fixes, as separating them into logical commits improves traceability, auditability, and overall Git history clarity.

Grouping files by feature improves Git history clarity because it organizes changes into logical sets that reflect specific tasks or fixes, making it easier to review, audit, and trace modifications over time.