git-commit

Name: git-commit
Availability: InStock
Author: sommio

Generate conventional git commit messages from the working tree and commit changes.

1|Updated Apr 3, 2026

Search Tags:#git #workflow #commit #version-control #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/sommio/RSSift --skill git-commit-sommio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/sommio/RSSift/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/sommio/RSSift --skill git-commit-sommio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a git commit with a clear, value-communicating message that follows repository conventions when they exist, or defaults to conventional commit format otherwise.

Core Features & Use Cases

Generates well-structured git commit messages from the current working tree, selecting conventional formats when no repo conventions exist.
Adapts to repo conventions when present, maintaining consistency with existing history.
Guides safe commits by gathering context (git status, diff, current branch, recent commits) and staging specific files for commit.

Quick Start

Tell me to commit your changes and I will craft a clear, conventional commit message and perform the commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate a conventional commit message automatically from my git working tree?▼

To generate a conventional commit message automatically, the Skill analyzes your git working tree context, including git status, diff, current branch, and recent commits. It then crafts a structured message and performs a targeted, safe commit.

Can I automate git commit messages to match my existing repository conventions?▼

Yes, you can automate git commit messages to match existing repository conventions. The Skill adapts to the conventions present in your repo history, maintaining consistency, or defaults to standard conventional commit format when no conventions exist.

What is the best way to write conventional commits for both staged and unstaged changes?▼

The best way to write conventional commits for staged and unstaged changes is to let the Skill gather your full git context. It evaluates both staged and unstaged changes, stages specific files safely, and generates a clear, value-communicating commit message.

Does this git commit workflow support analyzing recent commit history for context?▼

Yes, this git commit workflow supports analyzing recent commit history for context. It relies on recent commits alongside git status, diff, and current branch data to ensure the generated conventional commit message aligns with your repository's existing style.

How do I ensure a safe git commit without accidentally including unintended changes?▼

To ensure a safe git commit without unintended changes, the Skill performs a targeted commit by gathering comprehensive git context. It stages specific files for commit rather than blindly committing all modifications, preventing accidental inclusion of unrelated working tree changes.

What are the limitations of automating git commit message generation?▼

A limitation of automating git commit message generation is that the Skill applies to typical software development workflows. It relies entirely on analyzing git context like diff and status, meaning extremely complex or unconventional working tree changes may require manual message refinement.