git-commit

Enforce conventional commit prefixes and issue refs in Git messages.

3|2|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/poteto-go/go-alchemy-sdk --skill git-commit-poteto-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/poteto-go/go-alchemy-sdk/tree/main/.gemini/skills/git-commit
Command: npx skills add https://github.com/poteto-go/go-alchemy-sdk --skill git-commit-poteto-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit hygiene and traceability across Git repositories by enforcing conventional prefixes and issue linking.

Core Features & Use Cases

  • Prefix-based categorization: enforce prefixes like feat, fix, refactor, perf, test, chore, mig, docs, ci, style.
  • Issue linking: automatically include refs: #<issue-number> derived from branch names, ensuring traceability.
  • Co-Author Attribution: always include Co-Authored-By trailer to attribute AI assistant contributions.

Quick Start

Follow the commit rule to craft a message with a prefix and issue refs, then include the Co-Authored-By trailer.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I enforce conventional commit prefixes in a Git repository?

Conventional commit prefixes are enforced by applying a standardized message template that restricts commits to allowed types like feat, fix, refactor, and perf. This ensures commit hygiene and categorization across software development workflows.

How do I automatically link Git commits to issue numbers from a branch name?

To automatically link Git commits to issue tracking numbers, the commit format extracts refs from the branch name and includes them as refs: #<issue-number>. This ensures traceability across multiple repositories without manual input.

What is the correct format for adding a Co-Authored-By trailer in Git commits?

A Co-Authored-By trailer in Git commits attributes AI assistant contributions by appending a mandatory Co-Authored-By line to the commit message. This satisfies policy and audit requirements for AI-assisted software development workflows.

Can I use conventional commit linting in a CI pipeline across multiple repositories?

Conventional commit linting can be applied in CI pipelines across multiple repositories to enforce standardized prefixes, issue linking, and co-author attribution. This ensures traceable and well-structured commits satisfy policy and audit requirements.

What conventional commit prefixes are allowed for standardizing Git messages?

Allowed conventional commit prefixes for standardizing Git messages include feat, fix, refactor, perf, test, chore, mig, docs, ci, and style. This prefix-based categorization enforces commit hygiene and traceability across repositories.