skills.rest
YanBerdin
YanBerdinCOMMUNITY
Explore all skills by this author →
GitHub

commit

Generate conventional commit messages with enforced header format and allowed types.

2|Updated May 19, 2024
Search Tags:#git#workflow#commit#team-collaboration#version-control#conventional-commits
One-click install
npx skills add https://github.com/YanBerdin/next-portfolio --skill commit-yanberdin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/YanBerdin/next-portfolio/tree/main/.github/skills/commit
Command: npx skills add https://github.com/YanBerdin/next-portfolio --skill commit-yanberdin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many development teams struggle to maintain a consistent, readable Git history. Conventional commits provide a standardized format that makes changes easier to review, automate changelog generation, and track scope of work across releases.

Core Features & Use Cases

  • Enforces header formats like type(scope): subject to ensure consistency across commits.
  • Provides guidance and examples for common commit types (feat, fix, docs, chore, refactor, test, perf, style, build, ci, revert) and optional scopes.
  • Helps reference issues automatically, improving traceability and release notes.
  • Ideal for CI pipelines that validate commit messages before merging or generating changelogs.

Quick Start

Draft your first conventional commit using the header format described above.

Frequently Asked Questions about commit

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

FAQPage Schema
What are conventional commits and why use them in git workflows?▼

Conventional commits standardize git history using a type(scope): subject format, making changes easier to review, automating changelog generation, and tracking work scope across releases.

How do I write a conventional commit message for a feature or bugfix?▼

Format conventional commits as type(scope): subject, using allowed types like feat for features or fix for bugfixes, adding optional scopes to categorize the change area concisely.

Which conventional commit types and scopes are allowed for standardizing git history?▼

Allowed conventional commit types include feat, fix, docs, chore, refactor, test, perf, style, build, ci, and revert, with optional scopes to define the affected module in the git workflow.

Can I use conventional commit messages in CI pipelines to validate branches before merging?▼

Yes, conventional commits are ideal for CI pipelines to validate commit header formats, enforce subject length, and check issue references before merging branches or generating automated changelogs.

Does this commit standardization tool work without additional git dependencies or components?▼

Yes, it operates with no additional dependencies or components, enforcing conventional commit rules like header format, subject length, and allowed types directly within your version control workflow.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic
Asymmetric-alAsymmetric-al
417

commit

Generate Conventional Commit messages for staged Git changes with type, scope, and subject constraints.

Official
Intermediate