skills.rest
qlawmarq
qlawmarqCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate conventional Git commit messages from staged diffs.

Updated Dec 2, 2025
Search Tags:#git#code review#version control#commit#conventional commits#pre-commit hooks
One-click install
npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-commit-qlawmarq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/qlawmarq/dotfiles-common/tree/main/skills/git-commit
Command: npx skills add https://github.com/qlawmarq/dotfiles-common --skill git-commit-qlawmarq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted, conventional Git commit messages, ensuring code quality and maintainability by enforcing best practices and pre-commit checks.

Core Features & Use Cases

  • Automated Pre-Commit Checks: Runs linters, formatters, build verifications, and documentation updates before committing.
  • Intelligent Commit Splitting: Analyzes staged changes to suggest breaking down large commits into smaller, atomic units.
  • Conventional Commits: Generates commit messages adhering to the <type>: <description> format.
  • Sensitive Data Detection: Prevents accidental commits of secrets or PII.
  • Use Case: After completing a feature, use this skill to ensure your commit message is correctly formatted, all necessary checks pass, and the commit is atomic and descriptive.

Quick Start

Use the git-commit skill to generate a conventional commit message for the staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages from staged Git diffs?▼

You can generate conventional commit messages by analyzing staged Git diffs to automatically format changes into the <type>: <description> syntax, enforcing atomic commit practices and code quality standards.

What are conventional commits and how do pre-commit hooks enforce them?▼

Conventional commits use a <type>: <description> format to standardize version control history. Pre-commit hooks enforce them by automating linters, formatters, and build verifications before changes are committed to the repository.

Can I automatically split large Git commits into smaller atomic units?▼

Yes, you can automatically split large Git commits into smaller atomic units by analyzing staged changes. This intelligent commit splitting feature suggests breaking down large commits to improve code maintainability.

How do I prevent sensitive data and secrets from being committed to Git?▼

To prevent sensitive data and secrets from being committed to Git, this skill includes sensitive data detection that scans staged diffs for PII or secrets, ensuring accidental commits are blocked before they happen.

Does this skill support running linters and formatters as automated pre-commit checks?▼

Yes, this skill supports running linters and formatters as automated pre-commit checks. It automates these verifications alongside documentation updates and build checks to ensure code quality before generating a commit message.

Related Skills

Explore More Software Engineering Skills→
luicabref97luicabref97

git:commit

Create emoji-enhanced conventional commit messages for Git changes.

Community
Advanced
howdeployhowdeploy
15

ship

Automate the end-to-end ship workflow from branch to PR.

Community
Advanced
SchurupIK72SchurupIK72

commit-helper

Enforce Conventional Commits and atomic change limits in git workflows.

Community
Advanced
John2143John2143
2

commit-writer

Generate conventional Git commit messages from staged changes.

Community
Basic