commit

Generate conventional commit messages with type, scope, subject, body, and footer.

2.2k|444|Updated Nov 8, 2021
One-click install
npx skills add https://github.com/alibaba/loongcollector --skill commit-alibaba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/alibaba/loongcollector/tree/main/.cursor/skills/commit
Command: npx skills add https://github.com/alibaba/loongcollector --skill commit-alibaba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate conventional commit messages for code changes to ensure consistency and readability in version history and review processes.

Core Features & Use Cases

  • Generate commits that follow the Conventional Commits specification (type, scope, subject, body, footer).
  • Validate subject length and allowed type scopes to prevent non-conformant messages.
  • Use case: when preparing changes for release notes, changelogs, or automated workflows.

Quick Start

Provide a conventional commit message for the latest change.

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 automatically for code changes?

To generate conventional commit messages automatically, you apply the skill to your code changes. It outputs standardized messages with proper type, scope, subject length, body, and footer formatting per Conventional Commits guidelines.

What is the conventional commits specification for scannable git history?

The conventional commits specification structures git history by enforcing a standard message format. It requires specific types, optional scopes, controlled subject lengths, and structured body and footer content for automated workflows and changelogs.

How do I validate subject length and allowed type scopes for conventional commits?

You validate subject length and allowed type scopes by using automated guardrails during message generation. This prevents non-conformant messages, ensuring invalid type combinations do not break your standardized repository history.

Can I use automated commit message generation across multiple repositories and PRs?

Yes, automated commit message generation applies to software development workflows across multiple repositories and PRs. It ensures standardized, scannable version history for consistent release notes and review processes.

What are the limitations of conventional commit message automation?

Limitations of conventional commit message automation include strict adherence to allowed type and scope combinations. Guardrails prevent invalid combinations, meaning highly customized or non-standard commit formats may not be supported by the generation rules.