skills.rest
fengqiyu0317
fengqiyu0317COMMUNITY
Explore all skills by this author →
GitHub

commit-msg

Format git commit messages with structured tags, file paths, and descriptions.

1|Updated Dec 17, 2025
Search Tags:#git#workflow#commit#pre-commit#milestone#branch-naming#message
One-click install
npx skills add https://github.com/fengqiyu0317/assassyn --skill commit-msg-fengqiyu0317
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-msg
Source: https://github.com/fengqiyu0317/assassyn/tree/main/assassyn-master/.claude/skills/commit-msg
Command: npx skills add https://github.com/fengqiyu0317/assassyn --skill commit-msg-fengqiyu0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages should clearly describe the changes to a codebase and enable traceability, reducing confusion during reviews and future maintenance.

Core Features & Use Cases

  • Structured commit format: guidance on including a tag, affected files, and concise descriptions.
  • Milestone and branch guidance: supports milestone commits on development branches with associated issue references and branch naming conventions.
  • Pre-commit workflow alignment: aligns commit messaging with repository policies and project guidelines described in the skill.

Quick Start

Create a meaningful commit message for the staged changes following the defined structure and include any relevant milestone or issue references.

Frequently Asked Questions about commit-msg

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

FAQPage Schema
How do I format a git commit message for better code traceability?▼

To format a git commit message for traceability, use a structured format that includes a tag, affected file paths, and concise change descriptions. This ensures clarity during code reviews and future maintenance.

How do I include issue references and branch naming conventions in a milestone commit?▼

For milestone commits on development branches, include the associated issue references and adhere to branch naming conventions within your commit message. This aligns the commit with your project workflow guidelines.

Can I use pre-commit rules to validate my git commit messages?▼

Yes, you can validate git commit messages using pre-commit rules. Aligning your commit messaging with repository policies and pre-commit workflow guidelines ensures structured and compliant code changes.

What is the best way to structure commit messages for staged changes?▼

The best way to structure commit messages for staged changes is to follow a defined format incorporating a tag, affected files, and concise descriptions of the modifications made to the codebase.

Does this commit message formatting approach work with standard development branch workflows?▼

Yes, this commit message formatting approach works with standard development branch workflows. It specifically supports milestone commits and integrates branch naming conventions to guide message content effectively.

Related Skills

Explore More Software Engineering Skills→
sambersamber
178

conventional-git

Standardize Git commit messages and branch naming using Conventional Commits v1.0.0 rules.

Community
Advanced
malinskibeniaminmalinskibeniamin
3

commit-push-pr

Automate commit, push, and pull request creation with CI monitoring.

Community
Advanced
HyperxqHyperxq
1

lefthook

Enforce Conventional Commits and run Git hooks via Lefthook.

Community
Intermediate
sulhicmzsulhicmz

git-commit-message

Generate conventional commit messages from git diffs and staged changes.

Community
Intermediate