git-assistant

To generate conventional commit messages, the skill analyzes your `git diff --staged` output and automatically proposes a compliant commit message based on the current changes. This ensures your project history follows the Conventional Commits specification without manual formatting effort.

Yes, you can automatically generate branch names and PR descriptions by analyzing the git diff. The skill evaluates your staged changes to propose a descriptive branch name and draft a concise PR description alongside the commit message in a single output.

Automating changelog generation relies on consistently formatted commit messages. By using this skill to enforce Conventional Commits during commit preparation, you establish the structured message history required to automatically compile accurate changelogs.

No external dependencies are required to draft PR descriptions from git changes. The skill operates independently by analyzing your staged git diff to output the proposed commit message, branch name, and PR description directly.

Using Conventional Commits for your commit messages and branch names improves project hygiene and saves time. It enforces a consistent format that makes automated changelog generation possible and clarifies the scope of changes for team collaboration.

Automated conventional commit generation may not suit highly complex or nuanced changes where manual context is required. The skill proposes messages by analyzing `git diff --staged`, so manual review is recommended for changes with hidden architectural impacts.