git-commit

Generate conventional commit messages with type, scope, subject, body, and footer.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/saajunaid/junai --skill git-commit-saajunaid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/saajunaid/junai/tree/main/.github/skills/devops/git-commit
Command: npx skills add https://github.com/saajunaid/junai --skill git-commit-saajunaid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create well-structured conventional commit messages that follow the Conventional Commits standard, helping teams maintain a clean, traceable history.

Core Features & Use Cases

  • Generate commit messages that conform to types (feat, fix, docs, style, refactor, perf, test, chore, ci, build) and optional scopes.
  • Validate and format the subject, body, and footer, including breaking changes and issue references.
  • Use during committing changes, preparing PRs, and generating changelogs across projects.

Quick Start

Provide a well-formed commit message for the current changes following the Conventional Commits rules.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commit messages for my git workflow?

Use the skill to automatically format the commit type, optional scope, and subject. It validates the structure and appends optional body and footer for breaking changes and issue references.

What is the correct format for conventional commits with breaking changes?

Conventional commit format requires type(scope): subject. This skill formats your input and appends an optional body and footer to properly document breaking changes and issue references.

Can I use conventional commits to automate changelog generation across projects?

Yes, well-structured conventional commits enable changelog automation. This skill formats messages with correct types and scopes, ensuring a clean and traceable history for changelog generation across projects.

Does this conventional commit formatter support all standard commit types like feat and fix?

Yes, it supports standard types including feat, fix, docs, style, refactor, perf, test, chore, ci, and build. It applies these types with optional scopes to format your commit messages.

What's the best way to structure a git commit message for PR preparation?

The best way is using the conventional format. This skill ensures your PR commit message includes the correct type, optional scope, and subject to maintain a clean and traceable project history.