semantic-commits

Generate semantic commit messages with conventional type prefixes and PR narratives.

Updated Apr 1, 2026

Search Tags:#git #commit #pr #semantic #conventional-commits #message #subject

Ready to run

npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill semantic-commits-lilmuckers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: semantic-commits
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/semantic-commits
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill semantic-commits-lilmuckers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you generate semantic commit messages that are short, informative, and consistent, making Git histories easier to read and review.

Core Features & Use Cases

Semantic prefixes: Enforce conventional commit types (feat, fix, docs, etc.) for all commits.
Subject-first writing: Produce concise subjects while narrating broader context in PR descriptions.
PR narrative support: Provide justification and impact details to accompany code changes.

Quick Start

Generate a semantic commit message for the latest change with a concise subject and a detailed PR description.

Frequently Asked Questions about semantic-commits

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

FAQPage Schema

How do I generate semantic commit messages for Git changes?▼

To generate semantic commit messages, the Skill applies conventional commit guidelines to your code changes, producing concise subjects with appropriate type prefixes like feat or fix. It supports scope prefixes to keep Git histories readable and consistent.

What is the best way to write conventional commit subjects for pull requests?▼

Writing conventional commit subjects is done by enforcing a subject-first approach that keeps the commit message concise while moving broader context and justification into the PR description, creating a clear narrative for reviewers.

How do I add type and scope prefixes to my Git commit messages?▼

Adding type and scope prefixes to Git commit messages involves applying conventional commit guidelines during feature development or bug fixes, ensuring the subject remains informative and the Git history follows a consistent semantic structure.

Does this approach to semantic commits support PR narrative and justification?▼

Yes, semantic commits support PR narrative by generating a detailed pull request description that accompanies the concise commit subject, providing the broader context, impact details, and justification needed for code review.

When do I need conventional commit messages for my software project?▼

You need conventional commit messages during feature development, bug fixes, refactors, and documentation updates to improve Git history readability, making it easier to track changes and review code across software projects.