skills.rest
aurabx
aurabxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate Conventional Commits messages from working tree or staged diffs.

3|Updated May 26, 2026
Search Tags:#automation#git#commit#developer-tools#version-control#conventional-commits
One-click install
npx skills add https://github.com/aurabx/nightowl --skill git-commit-aurabx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/aurabx/nightowl/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/aurabx/nightowl --skill git-commit-aurabx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the inconsistency and lack of clarity in git commit histories by enforcing the Conventional Commits specification, ensuring every change is documented with a clear type, scope, and purpose.

Core Features & Use Cases

  • Conventional Commit Generation: Automatically analyzes code diffs to suggest appropriate commit types (feat, fix, refactor, etc.) and scopes.
  • Intelligent Staging: Provides guidance on grouping logical changes into atomic commits to maintain a clean project history.
  • Use Case: When you have finished a complex feature implementation, use this skill to analyze your staged changes and generate a perfectly formatted commit message that follows your project's semantic versioning standards.

Quick Start

Ask the git-commit skill to analyze your current staged changes and generate a conventional commit message for you.

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 commits automatically from staged changes?▼

You can generate a conventional commit by asking the skill to analyze your staged git diffs. It uses standard git CLI access to perform diff analysis and suggests a perfectly formatted semantic commit message with an appropriate type and scope.

What is the best way to maintain a clear git history with semantic versioning?▼

The best way to maintain clear git history for semantic versioning is to enforce the Conventional Commits specification. This skill automates that process by ensuring every code change is documented with a clear type, scope, and purpose based on the working tree diff.

Do I need standard git CLI access to use automated commit message generation?▼

Yes, you need standard git CLI access to use this automated commit message generation. The skill requires CLI access to perform the necessary diff analysis on your working tree or staged changes and to execute the final commit operations.

Can I group multiple staged changes into a single atomic git commit?▼

Yes, the skill provides intelligent staging guidance to help you group logical changes into atomic commits. By analyzing your working tree diffs, it ensures your project history remains clean and maintains standardized semantic versioning tracking.

How does conventional commit generation handle complex feature implementations?▼

Conventional commit generation handles complex implementations by analyzing the complete working tree diff to determine the correct commit type and scope. This ensures that even after finishing a complex feature, your commit follows the project's semantic versioning standards.

Related Skills

Explore More Software Engineering Skills→
blakecyzeblakecyze
2

kanso-commit

Analyze the working tree and create atomic git commits with imperative messages.

Community
Intermediate
ccfccf

changelog-automation

Generate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.

Community
Advanced
sustinbebustinsustinbebustin

commit

Guide staging and formatting of atomic conventional Git commits.

Community
Intermediate
onbjergonbjerg
4

commit

Generates Conventional Commits messages from local change status and diff tools.

Community
Basic