committing-changes

To automate conventional commit messages, the Skill inspects your current git changes, evaluates whether to split commits, and generates a compliant conventional commit message based on your project's rules. It then stages files and executes the commit after user confirmation.

The workflow handles splitting git commits by inspecting changes and evaluating whether multiple file modifications should be separated. It guides users through safe staging to ensure each commit represents a logical, conventional change set.

To enforce conventional commit rules, the Skill applies the project's commit conventions defined in its references and generates messages accordingly. This ensures consistent, auditable git history across multiple commits and workflows.

Yes, you can review the generated conventional commit message before execution. The workflow includes user confirmation and safety checks to prevent accidental pushes or unwanted changes, ensuring you maintain control over the version-control process.

No external dependencies are required to automate staging and committing changes. The Skill operates independently to inspect changes, apply commit rules, and execute the git commit workflow with built-in safety checks.

The primary limitation is that the workflow focuses on composing and executing local commits with user confirmation. It includes safety checks to prevent accidental pushes, meaning it does not automatically push changes to remote repositories.