task-flow-commit

Clean git commit messages clearly describe changes and intent by drafting concise summaries, matching repository conventions, and reviewing staged diffs before committing. This approach avoids auto-committing and requires explicit user approval for safety.

Generating a commit message from staged changes involves inspecting git status and git diff --staged, drafting a concise summary of the modifications, and appending the Co-Authored-By line before final approval. This ensures the message matches repository conventions.

To ensure your git workflow follows repository conventions, inspect git log to identify existing patterns, draft messages without tickets or prefixes unless already used, and selectively stage files to keep commits focused and readable for product teams.

No, you cannot automatically commit staged files without review. The workflow includes safety rails that prevent auto-committing, requiring explicit user approval and a review of the drafted message and staged files before finalizing the version control update.

Yes, this commit workflow supports adding a Co-Authored-By trailer automatically. It appends the Co-Authored-By: Claude line to the drafted message before presenting it for final user approval to ensure proper attribution.

You need to selectively stage changes when preparing a pull request to ensure commits are focused and human-readable. By reviewing git diff and staging specific files, you generate clear summaries of what changed and why to speed up code review.