commit

Analyze code changes and generate conventional commit messages.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Protagonistss/ithinku-plugins --skill commit-protagonistss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Protagonistss/ithinku-plugins/tree/main/plugins/git-tools/skills/commit
Command: npx skills add https://github.com/Protagonistss/ithinku-plugins --skill commit-protagonistss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

自动分析代码变更并生成符合规范的提交信息,减少人工撰写提交信息的时间和出错。

Core Features & Use Cases

  • 变更分析:识别文件类型和影响范围
  • 类型检测:自动识别 feat/fix/docs 等提交类型
  • Scope识别:自动确定变更模块
  • 信息生成:生成符合规范的提交信息
  • 质量检查:检查敏感信息、TOD0 等
  • 纯净提交:绝不在提交历史中留下 AI 工具标识,保持专业

Quick Start

请对最近的代码变更运行分析并生成符合提交规范的提交信息。

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate conventional commit messages from code changes?

You generate conventional commit messages by analyzing code diffs to detect types like feat or fix, identifying the scope, and validating for sensitive data before producing the final commit text.

What is conventional commit scope detection and how does it work?

Conventional commit scope detection works by analyzing code changes to automatically determine the affected module or component, ensuring the generated commit message accurately reflects the impact area of the modification.

How do I check my staged changes for sensitive data before committing?

Checking staged changes for sensitive data involves analyzing the diff to detect hardcoded secrets, TODOs, and other quality issues, preventing them from entering the commit history during automated message generation.

Can I generate git commit messages without leaving AI tool identifiers in the history?

Generating git commit messages without leaving AI tool identifiers is supported by enforcing clean commit outputs, ensuring the automated message preparation maintains a professional and pure version control history.

Does automated commit message generation work for code review preparation?

Automated commit message generation works for code review preparation by enforcing conventional commits and validating quality, which provides reviewers with standardized, descriptive context about the code changes.