commit

Generate conventional Git commits with proper identity and co-author trailers.

7|3|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/seabbs/claude-code-config --skill commit-seabbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/seabbs/claude-code-config/tree/main/skills/commit
Command: npx skills add https://github.com/seabbs/claude-code-config --skill commit-seabbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a standardized, conventional commit message with correct git identity to improve history readability and collaboration.

Core Features & Use Cases

  • Generate conventional commits with properly formatted types, scopes, and messages.
  • Configure git identity automatically based on mode and ensure a Co-authored-by trailer when required.
  • Improve code review and rollback processes by maintaining a clean, auditable history.

Quick Start

Use the commit skill to create a well-formed commit with a descriptive message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate creating conventional commits with the correct git identity?

You can automate conventional commits by configuring git identity per mode and enforcing commit types, scopes, and co-author trailers. This ensures a clean, auditable history across local development and CI pipelines.

What is a conventional commit and why do I need a co-author trailer?

A conventional commit standardizes message format with specific types and scopes to improve history readability. A co-author trailer appends collaborator attribution, enhancing code review and rollback processes.

Can I use this conventional commit automation in my CI pipeline?

Yes, this conventional commit automation applies to software projects using Git where consistent history and auditability are needed across local development and CI pipelines.

How do I configure git identity automatically based on my development mode?

Configuring git identity automatically based on mode requires a tool that sets user details per context. This ensures correct attribution and appends a Co-authored-by trailer when required for collaboration.

Does this commit automation prevent direct pushes to the main branch?

Yes, this commit automation prevents direct pushes to main to protect your primary branch. It enforces conventional commit types and proper identity configuration while safeguarding your codebase history.