auto-stage-commit

To automatically stage git changes and generate a conventional commit message, run the git working tree staging process to capture diffs, then delegate message formatting to ensure consistent commit semantics before executing git commit.

Yes, you can review the generated commit message before the git commit happens because the process stops to output staged file stats and a ready-to-run git commit command, preventing unintended commits.

Diff analysis for drafting a conventional commit works by running cached-aware git status and diff commands to extract context, which is then used to generate an appropriate commit message matching the project's preferred format.

No, the auto staging process does not require manual file selection because it runs git add -A to stage all changes automatically, although it can also use existing staged changes if they are already present.

The best way to maintain consistent commit semantics during a code workflow is to generate reviewable Conventional Commits messages automatically from diff context, ensuring your commit history matches the project's preferred formatting without manual effort.

If you signal commit intent without providing a message, your working tree is staged via git add -A and a lean conventional commit message is generated from the diff context, yielding a ready-to-run command without performing the commit itself.