commit

Generate conventional Git commit messages from staged changes.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/coreindustries/core-ai-template --skill commit-coreindustries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/coreindustries/core-ai-template/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/coreindustries/core-ai-template --skill commit-coreindustries

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commit messages, ensuring they adhere to conventional commit standards and include all necessary information for clear and consistent version control.

Core Features & Use Cases

  • Automated Message Generation: Analyzes staged changes to automatically generate a commit type, scope, and description.
  • Conventional Commits: Strictly follows the <type>(<scope>): <description> format.
  • Security Scanning: Prevents committing secrets or sensitive data.
  • Use Case: After making several changes to the authentication module, use this skill to generate a feat(auth): add password reset endpoint commit message with an optional body explaining the changes and closing relevant issues.

Quick Start

Use the commit skill to create a new commit message for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged Git changes?

To generate conventional commit messages, this Skill analyzes your staged Git changes to automatically determine the commit type, scope, and description, strictly following the `<type>(<scope>): <description>` format. It ensures atomic commits and prevents sensitive data inclusion.

Can I amend a previous Git commit or create a fixup commit?

Yes, you can amend previous Git commits and create fixup commits. This Skill supports modifying existing commit messages while maintaining the conventional commit standards, ensuring your version control history remains clean and consistent.

How does this Skill prevent committing secrets or sensitive data?

This Skill prevents committing secrets by performing security scanning on your staged changes. It analyzes the diff to detect sensitive data before generating the commit message, ensuring sensitive information is never accidentally included in your Git history.

What is the conventional commit format used for Git commit messages?

The conventional commit format used is `<type>(<scope>): <description>`. This Skill automatically generates this structure by analyzing your staged changes, adding an optional body to explain changes and closing relevant issues for clear version control.

Do I need to manually specify the scope and type for my Git commit?

No, you do not need to manually specify the scope and type. This Skill automates message generation by analyzing your staged changes to determine the appropriate commit type and scope, crafting a well-formatted Git commit message automatically.

What is the best way to ensure my Git commits are atomic and well-formatted?

The best way to ensure atomic, well-formatted Git commits is to use this Skill. It analyzes staged changes to generate conventional commit messages, enforcing strict formatting and preventing the inclusion of secrets for consistent version control.