skills.rest
qol-tools
qol-toolsOFFICIAL
Explore all skills by this author →
GitHub

commit

Generate conventional one-line Git commit messages with type prefixes.

Updated Apr 19, 2026
Search Tags:#automation#git#workflow#commit#safety#conventional
One-click install
npx skills add https://github.com/qol-tools/qol-skills --skill commit-qol-tools
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-dev-conventions/skills/commit
Command: npx skills add https://github.com/qol-tools/qol-skills --skill commit-qol-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers craft clear, conventional commit messages and maintain safe commit workflows, reducing ambiguity and accidental history changes.

Core Features & Use Cases

  • Conventional Commit Guidance: Suggests appropriate types (feat, fix, docs, chore) and ensures proper scope.
  • One-line Commit Messages: Generates concise, single-line messages suitable for automated tooling.
  • Safety Rules: Warns against pushing after committing and flags unsafe changes or broad file commits.

Quick Start

Generate a concise, one-line commit message for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

Conventional commit messages are generated by analyzing your staged changes and applying standard prefixes like feat, fix, docs, or chore. This ensures single-line messages with correct scopes for consistent history hygiene.

What is the best way to write safe git commit messages for team collaboration?▼

Safe git commit messages require concise single-line formats with conventional prefixes. The workflow flags broad, unrelated file changes and warns against immediate pushes, preventing accidental history alterations during team collaboration.

How do I choose the right conventional commit type for my changes?▼

Choosing the right conventional commit type means matching the change purpose: feat for features, fix for bugs, docs for documentation, and chore for maintenance. The workflow provides guidance to select correct prefixes and optional scopes.

Can I prevent accidental pushes when automating my git workflow?▼

Yes, preventing accidental pushes is possible by implementing safety rules that warn against pushing after committing. The workflow also flags broad, unrelated file changes to maintain repository history hygiene.

Why does my automated git commit workflow flag broad file changes?▼

Automated git commit workflows flag broad, unrelated file changes to enforce safety and maintain history hygiene. This safeguard prevents ambiguous commits, ensuring each commit remains focused and clearly documented.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced
TashanGKDTashanGKD
5

git-commit-conventions

Normalize and validate Git commits and pull requests against conventional commit standards.

Official
Advanced
lucidlabs-hqlucidlabs-hq
2

pr

Automate pull request workflows from branch creation to PR closure.

Official
Advanced
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate