commit

To create conventional git commits, this Skill guides you through reviewing changes, planning logical commit groupings, and safely staging specific files. It suggests Conventional Commits messages and prevents accidental inclusion of sensitive data by avoiding broad staging commands like `git add -A`.

The best way to split unrelated changes into separate git commits is to use a commit planning process that breaks down modifications into logical units. You selectively stage specific files for each unit, ensuring well-described commits for every logical group of work.

Safe staging prevents sensitive data from entering a git commit by guiding you to add specific files individually rather than using broad commands like `git add -A`. This targeted staging approach ensures only intended modifications are included in the version control history.

You need to use specific file staging commands instead of broad commands like `git add -A` to improve your development workflow with conventional commits. This practice ensures safe staging, prevents accidental sensitive data inclusion, and maintains a clear commit history.

You should avoid using `git add -A` for version control when your codebase contains unrelated changes or sensitive data. Instead, safely stage specific files individually to prevent accidental inclusions and ensure your git commit history remains clear and logical.