commit

Name: commit
Availability: InStock
Author: SUN-Underwriting

Generate Conventional Commits messages with type, scope, and description.

Updated Aug 27, 2026

Search Tags:#git #developer tools #code review #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/SUN-Underwriting/SunFlowCRM_DB --skill commit-sun-underwriting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SUN-Underwriting/SunFlowCRM_DB/tree/main/.agent/skills/commit
Command: npx skills add https://github.com/SUN-Underwriting/SunFlowCRM_DB --skill commit-sun-underwriting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and config (resource) components.

What problem does it solve?

This Skill automates the creation of Git commits that adhere to the Conventional Commits specification, ensuring a clean, consistent, and machine-readable commit history.

Core Features & Use Cases

Automated Commit Message Generation: Guides users through creating commit messages with correct types, scopes, and descriptions.
Branch Naming Convention Enforcement: Suggests branch prefixes based on commit type.
Use Case: When you've finished a new feature, use this skill to generate a feat commit message, ensuring it follows the project's standards and includes relevant details.

Quick Start

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

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate Git commit messages that follow the Conventional Commits specification?▼

To generate Conventional Commits messages, this Skill analyzes your staged Git changes and automatically determines the correct commit type, scope, and description. It then prompts for user confirmation before executing the commit to ensure accuracy.

What is the best way to automate semantic versioning and changelog generation from my commits?▼

Automating semantic versioning and changelog generation requires standardizing commit messages. This Skill enforces the Conventional Commits specification, creating a clean, machine-readable commit history that facilitates automated changelog generation.

How does Conventional Commits handle commit types and scopes for new features?▼

Conventional Commits handles new features by requiring a specific structure. This Skill analyzes your staged changes, determines the appropriate type like feat, assigns a scope, and drafts a description to ensure your feature commit follows project standards.

Can I enforce branch naming conventions based on my Git commit type?▼

Yes, you can enforce branch naming conventions based on commit type. This Skill suggests branch prefixes derived from the determined Conventional Commits type, ensuring your branch naming aligns with the project-specific rules.

Does this commit message generator require manual staging of files before use?▼

Yes, this commit message generator requires manually staged Git files. The Skill analyzes the staged changes to determine the correct Conventional Commits type and scope, then asks for user confirmation before executing the final commit.

Why should I use Conventional Commits instead of writing freeform Git commit messages?▼

You should use Conventional Commits instead of freeform messages to maintain a clean, consistent, and machine-readable commit history. This standardization facilitates automated changelog generation and semantic versioning for your project.