commit-convention

Analyze Git commit history to infer and apply project style.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ab300819/skills --skill commit-convention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-convention
Source: https://github.com/ab300819/skills/tree/main/commit-convention
Command: npx skills add https://github.com/ab300819/skills --skill commit-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

该 Skill 专注于在团队协作中统一 Git 提交信息的格式和风格,提升代码审阅效率与变更可溯性。

Core Features & Use Cases

  • 风格学习与模仿:在提交前分析项目历史提交,识别现有的前缀、语言和结构并优先模仿以保持一致性。
  • 规范回退与回退策略:当历史无明显规律时,遵循 Conventional Commits 规范进行风格化处理,确保可维护性。
  • 快速落地使用场景:提供清晰的提交信息示例和工作流指引,帮助团队在实际开发中快速执行规范。

Quick Start

在下一次提交前,先查看项目历史以确定风格,然后使用符合规范的提交信息,例如: git commit -m "feat(auth): add login flow"

Frequently Asked Questions about commit-convention

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

FAQPage Schema
How do I standardize Git commit messages across my team?

This skill standardizes Git commit messages by analyzing historical commits to infer and apply your project's existing style, enforcing a concise subject and optional body. It falls back to Conventional Commits when historical patterns are unclear.

What is Conventional Commits and when is it applied?

Conventional Commits is a structured formatting specification used as a fallback style when your project history shows no obvious commit patterns. It provides a standardized structure for concise subjects and optional bodies to ensure maintainability.

How do I write a Conventional Commits message for a new feature?

You write a Conventional Commits message by using a structured format with a concise subject and optional body, such as: git commit -m "feat(auth): add login flow". The skill guides this decision by inspecting your project history.

Can I use my existing Git workflow with this commit style guide?

Yes, you can use your existing Git workflow because the skill inspects historical commits to mimic your current style. It provides decision guidance for standardizing version control messages without disrupting your established development process.

What if my project history has no clear commit style?

If your project history has no clear commit style, the skill falls back to the Conventional Commits specification. This ensures your version control messages remain structured and maintainable by enforcing a concise subject and an optional body.