semaphore-commit

Creates conventional commit messages from staged git changes.

14.1k|1.3k|Updated Aug 23, 2014
One-click install
npx skills add https://github.com/semaphoreui/semaphore --skill semaphore-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semaphore-commit
Source: https://github.com/semaphoreui/semaphore/tree/main/.claude/skills/semaphore-commit
Command: npx skills add https://github.com/semaphoreui/semaphore --skill semaphore-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent, well-formatted git commit messages is repetitive and often inconsistent across a team. This Skill analyzes your staged changes and generates a commit message that follows the Conventional Commits specification automatically.

Core Features & Use Cases

  • Staged Diff Analysis: Inspects git diff --staged output to understand what actually changed before writing the message.
  • Conventional Commit Format: Produces messages in the <type>(<scope>): <description> format with types like feat, fix, docs, style, refactor, test, chore, and agents.
  • Clean Footer Policy: Commits are created without AI co-author attribution footers, keeping history clean.
  • Use Case: After staging changes to an authentication module, invoke the Skill to produce a commit like feat(auth): add password reset functionality with a structured body listing the changes.

Quick Start

Stage your changes with git add, then ask the assistant to create a conventional commit for the staged changes.

Frequently Asked Questions about semaphore-commit

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

FAQPage Schema
How do I write a conventional commit message?

A conventional commit uses the format type(scope): description, where type is one of feat, fix, docs, style, refactor, test, or chore. This Skill generates the message automatically by analyzing your staged changes with git diff --staged.

How to generate a git commit message from staged changes?

Stage your files with git add, then invoke the Skill. It runs git diff --staged to inspect the changes, selects the appropriate conventional commit type, and creates the commit with proper formatting.

What commit types does the conventional commits format support?

This Skill supports feat for new features, fix for bug fixes, docs for documentation, style for code style changes, refactor for restructuring, test for test changes, chore for maintenance, and agents for AI agent related work.

Does the commit include a Co-Authored-By Claude footer?

No. The Skill explicitly omits the Co-Authored-By Claude footer from generated commits, so your git history contains only the conventional commit message without AI attribution trailers.

Why does the commit message generation need staged changes?

The Skill analyzes git diff --staged output to understand what changed, so unstaged or untracked modifications are not considered. Stage all intended files with git add before generating the commit message.