git-commit-standard

To write conventional commit messages for your git diff, review the actual changes, stage only relevant files, and generate an English message with a required body detailing the rationale to ensure clear history and precise change tracking.

The best way to stage specific files before committing is to review the current diff and selectively stage only the intended files. This prevents accidental commits of unrelated changes and maintains a clean, focused commit history.

To ensure your git commit includes a detailed body for code review, generate a conventional commit message that requires a body section providing context and rationale for the changes, moving beyond simple one-line summaries.

No, you cannot automatically push changes after generating a conventional commit. Guardrails explicitly prevent pushing or amending commits unless explicitly requested by the user, ensuring safe staging and manual control over repository updates.

Yes, this conventional commit approach works with existing branching strategies. It focuses on reviewing diffs and staging relevant files locally before writing English conventional commit messages, integrating smoothly without altering your branch workflow.