commit

To generate conventional commit messages from git diff, the Skill analyzes staged and unstaged changes alongside recent commit history, then drafts an appropriate type like feat or fix based on the detected intent. It targets the correct conventional category by evaluating what changed and why.

Writing a conventional commit message from staged changes requires analyzing the cached diff to determine the change type. This Skill automates that by running git diff --cached, selecting a type from feat, fix, refactor, docs, test, chore, perf, or ci, and describing the intent clearly.

Yes, you can commit git changes using natural language commands like /commit, save changes, or 커밋. The Skill interprets these prompts, checks git status and diffs, stages changes safely, and executes the commit with a formatted conventional message.

A commit message generator handles empty commits and potential secrets by blocking empty commits entirely and encouraging targeted staging of specific files. It verifies success with git status after committing to ensure no unintended secrets are included.

You need to run git diff and git log before drafting a commit message when you want the new commit to match your repository's existing style. The Skill collects recent log references and current diffs to inform the correct conventional commit type and description.

This conventional commit tool works with staged and unstaged repository workflows by running git diff and git diff --cached to gather changes. It stages changes safely before committing and verifies the final repository state with git status.