commit

Generate conventional Git commits with emoji prefixes and GPG signing.

5|Updated Nov 6, 2025

Search Tags:#git #workflow #commit #pre-commit #conventional-commits #gpg-sign

Ready to run

npx skills add https://github.com/pigfoot/claude-code-hubs --skill commit-pigfoot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/pigfoot/claude-code-hubs/tree/main/plugins/commit/skills/commit
Command: npx skills add https://github.com/pigfoot/claude-code-hubs --skill commit-pigfoot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates well-formatted commits following conventional commit standards with emoji prefixes and GPG signing support, reducing cognitive load and enabling better history and tooling integration.

Core Features & Use Cases

GPG signing with a cached passphrase (if $GPG_PASSPHRASE is set)
Staged vs unstaged detection - commits only staged files when present
Split suggestions - analyzes diffs for multiple logical changes
Conventional commits - <emoji> <type>: <description> format
Pre-commit hook integration - respects Husky/other hooks
Always --signoff - DCO compliance

Quick Start

Use the commit skill when you say "commit", "commit these changes", or use the command /commit. Example: After making changes, say "commit these changes" to create a conventional, signed commit for staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create conventional commits with proper formatting?▼

Conventional commits use a standardized format: <emoji> <type>: <description>. This Skill automatically generates commits following this standard, keeping the first line under 72 characters, and integrates with Git workflows to enforce consistency across your project history.

Can I automatically sign commits with GPG?▼

Yes. This Skill signs commits with GPG when a passphrase is available via the $GPG_PASSPHRASE environment variable, and enforces --signoff for DCO compliance, ensuring authenticated and verifiable commit records.

What happens when I have both staged and unstaged changes?▼

This Skill detects staged versus unstaged files and commits only staged changes by default. It analyzes diffs to identify multiple logical concerns and suggests splitting large changes into separate commits for cleaner history.

Does this work with pre-commit hooks like Husky?▼

Yes. This Skill respects pre-commit hooks, integrating with frameworks like Husky so your commits pass configured validation checks before being finalized.

How do I trigger a commit using this Skill?▼

Use natural language commands like "commit", "commit these changes", or the `/commit` command after staging your changes. The Skill handles formatting, signing, and hook integration automatically.

Why should I use conventional commits over ad-hoc messages?▼

Conventional commits reduce cognitive load, enable better tooling integration (changelogs, release automation, history parsing), and create searchable, semantically meaningful Git history that teams can navigate and maintain easily.