skills.rest
SergeuMatyasov
SergeuMatyasovCOMMUNITY
Explore all skills by this author →
GitHub

commit-messages

Generate commit messages matching the format ticket type(scope: subject.

Updated Apr 9, 2026
Search Tags:#git#scope#version-control#conventional-commits#commit-messages#subject#ticket-number
One-click install
npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill commit-messages-sergeumatyasov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/SergeuMatyasov/dotnet-shared-skills/tree/main/commit-messages
Command: npx skills add https://github.com/SergeuMatyasov/dotnet-shared-skills --skill commit-messages-sergeumatyasov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Используя этот скилл, вы фиксируете единый формат commit message: номер задачи, Conventional Commits, scope, subject и body, что обеспечивает тесную связь истории изменений с задачами, читабельность и облегчает ревью.

Core Features & Use Cases

  • Обеспечивает единообразный шаблон сообщений для новых коммитов, squash и релизов.
  • Поддерживает требования к номеру задачи, типу, области и краткому описанию, упрощающими поиск истории.
  • Предлагает готовое сообщение после правок и для копирования в терминал или Git UI.

Quick Start

Create a single commit message using the exact format <ticket> <type>(<scope>): <subject> and add a concise body only for non-trivial changes.

Frequently Asked Questions about commit-messages

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

FAQPage Schema
How do I standardize git commit messages with a ticket number and conventional commits format?▼

Standardize git commit messages by enforcing the format `<ticket> <type>(<scope>): <subject>` with an optional body for non-trivial changes, ensuring traceability between version control history and project tasks.

What is the conventional commits format for linking a ticket number to a commit subject?▼

The conventional commits format for linking tickets requires placing the ticket number first, followed by the type, scope in parentheses, and a concise subject, creating a standardized message structure for clear software development history.

How do I write a standardized commit message for code reviews and release processes?▼

Write a standardized commit message for code reviews by applying the ticket-linked conventional commits template, which standardizes history and provides a ready-to-copy message for your terminal or Git UI after code modifications.

Can I use this commit message format for squash commits and release notes?▼

Yes, the commit message format applies to squash commits and release processes, maintaining a consistent template that includes the ticket number, type, scope, and subject to improve readability during software development workflows.

When should I include a body in my conventional commit message?▼

Include a body in your conventional commit message only for non-trivial changes, keeping the subject line concise while providing necessary context for complex updates within your version control history.

Related Skills

Explore More Software Engineering Skills→
jeremylongshorejeremylongshore
1

commit-message-writer

Generates formatted commit messages from staged changes.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
hypershift-communityhypershift-community

Git Commit Format

Enforce Conventional Commit formatting for HyperShift Git commits.

Official
Basic
TibsfoxTibsfox
69

git-commit

Generate Angular-format conventional commit messages from user prompts.

Community
Intermediate