skills.rest
ihmorol
ihmorolCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate standardized Git commit messages following the Conventional Commits specification.

1|2|Updated Jan 15, 2026
Search Tags:#git#developer tools#version control#commit#conventional commits#code history
One-click install
npx skills add https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids --skill git-commit-ihmorol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids/tree/main/.opencode/skills/git-commit
Command: npx skills add https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids --skill git-commit-ihmorol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create clear, meaningful, and structured Git commit messages that adhere to the Conventional Commits standard, improving code history readability and automation.

Core Features & Use Cases

  • Standardized Commit Format: Enforces a consistent structure for commit messages (<type>(<scope>): <subject>\n\n<body>\n\n<footer>).
  • Type and Scope Guidance: Provides a list of conventional commit types (feat, fix, docs, etc.) and explains the optional scope.
  • Subject and Body Best Practices: Offers guidelines for writing concise subjects and informative bodies.
  • Issue Tracking Integration: Facilitates referencing issues using standard footer formats (e.g., Fixes #123).
  • Use Case: Before committing code changes, use this Skill to generate a commit message that accurately describes the changes, such as feat(auth): implement two-factor authentication with a detailed explanation of the implementation.

Quick Start

Use the git-commit skill to generate a commit message for a bug fix in the user authentication module, referencing issue #456.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commit messages for git?▼

Git conventional commits use a `<type>(<scope>): <subject>` format to create clear, machine-readable commit logs. This standardizes types like feat or fix, and guides body content for automated changelog generation and semantic versioning.

What is the conventional commits format and when do I need it?▼

The conventional commits specification structures git messages into types, scopes, subjects, bodies, and footers. You need this format to improve code history readability and enable automated semantic versioning and changelog generation.

How do I reference an issue in a git commit message footer?▼

You reference issues in a git commit message footer using standard formats like `Fixes #123`. This integrates issue tracking directly into your code history while maintaining the conventional commits structure.

Can I generate a conventional commit message for a bug fix automatically?▼

Generating a conventional commit message for a bug fix involves using the `fix` type with an optional scope, such as `fix(auth): resolve login timeout`. This creates an informative, structured entry for the code history.

Related Skills

Explore More Software Engineering Skills→
navidemadnavidemad

publish

Generate conventional commit messages and GitHub pull request descriptions.

Community
Intermediate
xloxn69xloxn69
7

agileflow-commit-messages

Format git commit messages using the Conventional Commits specification.

Community
Basic
a-taka-tak
1

git-create-pr

Commit changes, push to origin, and create a GitHub Pull Request.

Community
Intermediate
k97k97
4

gen-release-notes

Generate structured release notes from git commit history and pull request data.

Community
Advanced