skills.rest
chapzin
chapzinCOMMUNITY
Explore all skills by this author →
𝕏@nerdlinuxGitHub

Commit Message

Generate conventional commit messages with automatic scope detection from changed files.

1|1|Updated May 7, 2026
Search Tags:#automation#git#commit#formatting#scope#conventional
One-click install
npx skills add https://github.com/chapzin/jcode-harness --skill commit-message-chapzin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Message
Source: https://github.com/chapzin/jcode-harness/tree/main/.context/skills/commit-message
Command: npx skills add https://github.com/chapzin/jcode-harness --skill commit-message-chapzin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create standardized commit messages that follow conventional commits, ensuring clear history and easier versioning.

Core Features & Use Cases

  • Detects scope from changed files and formats messages according to conventional commits.
  • Supports common types like feat, fix, docs, chore, and refactor with deterministic formatting.
  • Integrates with git workflows and helps maintain a clean, searchable project history.

Quick Start

Generate a conventional commit message for your most recent change, with an automatically detected scope.

Frequently Asked Questions about Commit Message

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

To generate conventional commit messages automatically, this skill analyzes your code changes to detect the scope and formats the message using standard types like feat, fix, docs, and chore for clean history.

What is automatic scope detection in git commits?▼

Automatic scope detection in git commits identifies the affected application layer from changed files, ensuring your conventional commit message accurately reflects whether the update targets frontend, backend, or tooling workflows.

Does this tool support formatting commit types like fix, feat, and chore?▼

Yes, it supports formatting common conventional commit types including feat, fix, docs, chore, and refactor, applying deterministic formatting to ensure standardized, searchable project history across git workflows.

How do I format frontend and backend changes in one commit?▼

Formatting frontend and backend changes in one commit is handled by detecting the modified files to determine the correct scope, ensuring the conventional commit message applies deterministic formatting across your tooling workflows.

When do I need conventional commits for my git workflow?▼

You need conventional commits for your git workflow when you want to ensure clear project history and easier versioning, applying deterministic formatting to code changes across feature, fix, docs, and chore categories.

Related Skills

Explore More Software Engineering Skills→
enzopitaenzopita

git-commit

Generate Conventional Commits messages from Git diffs and staged changes.

Community
Intermediate
motormetricsmotormetrics
21

release-management

Automate versioning and changelog generation across a monorepo with semantic-release.

Official
Advanced
ysoftmanysoftman
9

commit

Review changes, lint/format files, and create an English commit message.

Community
Intermediate
BSteffaniakBSteffaniak

commit-message

Generate a git commit message with title and description for current changes.

Community
Basic