commit

Generate conventional commit messages and execute signed git commits.

3.4k|728|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/linuxfoundation/crowd.dev --skill commit-linuxfoundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/linuxfoundation/crowd.dev/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/linuxfoundation/crowd.dev --skill commit-linuxfoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit automation that ensures every change is recorded with a properly formatted, signed commit message.

Core Features & Use Cases

  • Inspect staged changes and verify there is something to commit.
  • Generate a conventional commit message, optionally appending a CM ticket number from the branch name, and perform git commit -s -S.
  • Ensure sign-off and adherence to Conventional Commits standards for consistent history.

Quick Start

Generate and apply a signed commit message for the currently staged changes.

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 for staged changes?

You can automatically generate conventional commit messages by inspecting staged changes, deriving the current branch, and executing git commit -s -S. This ensures sign-off and adherence to Conventional Commits standards for consistent history.

What is the best way to append a CM ticket number to a git commit?

The best way to append a CM ticket number is to extract it from the current branch name and optionally append it to the generated conventional commit message before executing git commit -s -S.

How does signed-off-by commit automation work across software projects?

Signed-off-by commit automation works by inspecting staged changes, generating a compliant message, and executing git commit -s -S across software projects to enforce consistent commit history with sign-off.

Can I use branch name parsing to fulfill conventional commits standards automatically?

Yes, you can use branch name parsing to derive a CM ticket number and optionally append it to the conventional commit message, ensuring the commit fulfills Conventional Commits standards automatically.

Do I need staged changes to generate a signed commit message?

Yes, you need staged changes. The automation inspects staged changes to verify there is something to commit before generating a compliant message and executing git commit -s -S.

Why does my automated commit process require both sign-off and GPG signing?

Your automated commit process requires sign-off and GPG signing because the automation executes git commit -s -S, ensuring every change is recorded with a properly formatted, signed commit message to enforce consistent history.