git-commit

To generate a conventional commit message, the Skill analyzes your current working tree, detects repo-specific conventions or recent history, selectively stages files, and applies a properly formatted commit using a heredoc.

Handling a git commit in a detached HEAD state requires safe branch management; the Skill guides you through creating or switching to a feature branch before staging files and applying the commit to preserve your history.

To avoid committing sensitive files during a git commit, the Skill provides guidance on selective staging, allowing you to review and choose specific files from your working tree rather than committing everything blindly.

The git commit tool first checks for repo-specific commit conventions, then falls back to analyzing your recent commit history, and finally defaults to standard conventional commits to ensure properly formatted messages.

Your git workflow needs a feature branch before creating a commit to ensure safe branch handling; the Skill suggests creating one if you are in a detached HEAD state or lack an active branch to receive the staged changes.

Yes, you can automate creating a single git commit from unstaged changes; the Skill manages the entire working tree, stages files selectively, and generates one well-structured commit message aligned with your version-control conventions.