skills.rest
omarluq
omarluqCOMMUNITY
Explore all skills by this author →
Website𝕏@omarluqqGitHub

conventional-git

Enforce Conventional Commits v1.0.0 standards for branches, worktrees, and commit messages.

5|1|Updated Apr 14, 2026
Search Tags:#git#workflow#worktrees#conventional-commits#branch-naming#commit-messages
One-click install
npx skills add https://github.com/omarluq/og-template --skill conventional-git-omarluq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-git
Source: https://github.com/omarluq/og-template/tree/main/.agents/skills/conventional-git
Command: npx skills add https://github.com/omarluq/og-template --skill conventional-git-omarluq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards help teams achieve consistent git history, predictable release notes, and easier changelog automation across GitHub and GitLab projects.

Core Features & Use Cases

  • Branch Naming: Format: <type>/[issue-]<description> — lowercase, hyphenated, and aligned with issue numbers to enable traceability.
  • Worktree Naming: Place local worktrees under .claude/worktrees/ and name them by replacing the branch separator / with -; worktrees are local checkouts and never appear in remote branches.
  • Commit Message Format: Use subject/body structure with type, optional scope, and imperative description; enforce breaking-change indicators and footer references for issue closure and cross-repo links.

Quick Start

Apply the Conventional Git rules to your project by naming branches, worktrees, and commits according to the standards.

Frequently Asked Questions about conventional-git

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

FAQPage Schema
How do I format conventional commit messages for git?▼

Conventional commit messages require a subject with a type, optional scope, and imperative description, plus a body. You must enforce breaking-change indicators and use footers for issue closure and cross-repo references.

What is the correct branch naming format for conventional commits?▼

Branch naming follows the format <type>/[issue-]<description>, using lowercase and hyphens. Aligning branch names with issue numbers enables traceability across GitHub and GitLab projects.

How do I name git worktrees to match conventional branch naming?▼

Git worktrees belong under .claude/worktrees/ and are named by replacing the branch separator / with -. Worktrees are local checkouts only and never appear in remote branches.

Does conventional git work with both GitHub and GitLab projects?▼

Yes, conventional git standards apply across GitHub and GitLab projects. They enforce consistent git history, predictable release notes, and easier changelog automation on both platforms.

How do I indicate breaking changes in conventional commit messages?▼

Breaking changes are indicated using BREAKING CHANGE in the commit footer or an exclamation mark ! before the colon. This ensures automated tools correctly identify major version bumps.

When do I need conventional commits and worktree naming standards?▼

You need conventional commits when creating branches, naming worktrees, writing commit messages, or setting up changelog automation. They provide consistent git history and predictable release notes.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
leodyversemilla07leodyversemilla07

git-workflow

Enforce conventional commit messages and branch naming conventions in Git workflows.

Community
Basic
masa-codehubmasa-codehub

recording-changes

Stage changes and emit compliant git commit messages with branch validation.

Community
Intermediate