skills.rest
thomassloboda
thomasslobodaCOMMUNITY
Explore all skills by this author →
Website𝕏@slobodathomasGitHub

git-conventional-commit-writing

Analyze git worktree changes and propose conventional commit messages with ticket extraction.

1|Updated Apr 2, 2026
Search Tags:#git#commits#version-control#conventional-commits#branch-ticket-extraction#worktree-analysis
One-click install
npx skills add https://github.com/thomassloboda/ai-stuff --skill git-conventional-commit-writing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventional-commit-writing
Source: https://github.com/thomassloboda/ai-stuff/tree/main/skills/git-conventional-commit-writing
Command: npx skills add https://github.com/thomassloboda/ai-stuff --skill git-conventional-commit-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Proposes clean, conventional commit messages by analyzing the current git worktree and extracting project ticket information from the branch name when possible.

Core Features & Use Cases

  • Analyzes the current branch, staged changes, unstaged changes, and changed files to infer the dominant intent.
  • Proposes one or more commit messages that follow Conventional Commits and optionally include a ticket like [PROJ-123].
  • Applies branch-ticket-extraction and conventional-commit rules to craft a concise subject and an informative body when needed.

Quick Start

Run the git-conventional-commit-writing skill against your repository to generate a recommended commit message for the current worktree.

Frequently Asked Questions about git-conventional-commit-writing

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

FAQPage Schema
How do I generate conventional commit messages from my current git worktree?▼

Generate conventional commit messages by analyzing your git worktree to identify staged and unstaged changes, inferring the dominant intent, and proposing a cohesive commit message with an appropriate type and scope.

Can I automatically extract a project ticket number from my git branch name for commit messages?▼

Yes, branch-ticket-extraction analyzes your current git branch name to automatically detect and append project ticket identifiers like [PROJ-123] to your conventional commit messages.

What happens if my staged git changes contain multiple distinct intents?▼

When multiple distinct intents are detected in your staged changes, the analysis suggests splitting the worktree changes into multiple separate commits rather than forcing a single cohesive message.

Does this conventional commit writer evaluate both staged and unstaged git changes?▼

Yes, the worktree analysis evaluates both staged and unstaged changes alongside changed files to accurately determine the dominant intent and craft a concise subject with an informative body.

When do I need conventional commits with an optional scope for my version control workflow?▼

You need conventional commits with an optional scope when your version control workflow requires structured, semantic commit history that clearly communicates the type and context of applied changes.

Related Skills

Explore More Software Engineering Skills→
jvm-skillsjvm-skills
135

commit

Group unstaged Git changes into logical commits with concise messages.

Official
Intermediate
dascarddascard
2

chinese-commit-conventions

Standardize Git commit messages with Conventional Commits for Chinese teams.

Community
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
xloxn69xloxn69
7

agileflow-commit-messages

Format git commit messages using the Conventional Commits specification.

Community
Basic