commit

Enforce conventional commit messages with type, scope, body, and Co-Authored-By footer.

70|42|Updated Mar 27, 2026

Search Tags:#git #workflow #commit #code-quality #issue-tracking #conventional-commits #commit-guidelines

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill commit-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent or improperly formatted git commits by insisting on conventional commit syntax, issue references, and AI attribution every time changes are saved.

Core Features & Use Cases

Conventional commit structure: Headers must include a type, optional scope, subject under 70 characters, a body that explains what and why, and a footer with issue references or breaking changes.
Branch awareness and AI attribution: Verify the current branch, seek confirmation before committing to main or master, and append Co-Authored-By lines when changes originate from AI agents.
Use Case: When finishing a bug fix on a feature branch, follow this guidance to add the correct type, describe the fix motivation, reference the issue, and credit AI contributions.

Quick Start

Ask the commit skill to format your git commit message with type, scope, description, body motivation, and issue references before saving changes.

Frequently Asked Questions about commit

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

FAQPage Schema

What are conventional commits and why use them for git changes?▼

Conventional commits structure git commit messages with a type, optional scope, and subject to keep history readable and traceable. This format enforces consistent headers, descriptive bodies, and issue references for every change.

How do I format a git commit message with conventional commit guidelines?▼

Format git commit messages by including a type, optional scope, and a subject under 70 characters. Add a descriptive body explaining what and why, then append a footer with issue references and a Co-Authored-By line for AI contributions.

How do I add issue references and AI attribution to a commit message?▼

Add issue references in the commit message footer and append a Co-Authored-By line to credit AI-generated work. This ensures every change remains traceable to its originating issue and properly attributes AI agent contributions.

Can I use conventional commit syntax on any git branch?▼

Yes, conventional commit syntax applies to any branch. The workflow verifies the current branch and seeks confirmation before committing to main or master, ensuring readable and traceable history across all development branches.

What is the character limit for a conventional commit header?▼

The conventional commit header has a 70 character limit for the subject line. This constraint ensures git history remains readable and concise while still requiring a descriptive body for context.

Why does my git commit fail without a Co-Authored-By footer?▼

Git commits fail without a Co-Authored-By footer because this workflow enforces AI attribution for changes originating from AI agents. Appending this line is required to maintain traceability and proper credit in the commit history.