skills.rest
yxc023
yxc023COMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Generate conventional git commit messages from working tree changes.

Updated Apr 22, 2026
Search Tags:#git#messaging#workflow#commit#codebase#version-control#conventional-commits
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill git-commit-yxc023
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/git-commit
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill git-commit-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git commits with clear, value-communicating messages from the current working tree changes, reducing guesswork and rework.

Core Features & Use Cases

  • Generates conventional-commit-formatted messages by analyzing git status and diffs.
  • Honors repository-specific conventions when they exist and falls back to the conventional commits standard otherwise.
  • Supports committing both staged and unstaged changes, with optional scope extraction based on changes.

Quick Start

Create a single, well-structured git commit from the current working tree 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 git working tree changes?▼

You can automate git commit message creation by analyzing your current working tree changes, determining the commit type and scope from repository conventions or recent history, staging specified files, and issuing a single structured commit.

What is the best way to keep git commit messages consistent across a software team?▼

The best way to keep git commit messages consistent is to enforce conventional commits standards, honoring repository-specific conventions when they exist and falling back to the conventional commits standard otherwise to reduce guesswork and rework.

Can I create a structured git commit from both staged and unstaged changes?▼

Yes, you can commit both staged and unstaged changes from your working tree by analyzing the diffs, extracting optional scope based on the modifications, staging the specified files, and issuing a single structured git commit.

Does this workflow support extracting commit scope automatically from codebase diffs?▼

Yes, the workflow supports optional scope extraction based on codebase changes by analyzing the git status and diffs to determine the appropriate commit type, scope, and description for your working tree modifications.

Why do my automated git commits fail to match existing repository conventions?▼

Automated git commits might mismatch existing conventions if the tool does not analyze your recent commit history or honor repository-specific conventions, falling back to standard conventional commits instead of matching your team's specific format.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
gokulkrishhgokulkrishh
3

commit

Generate Conventional Commits compliant git commit messages from code changes.

Community
Intermediate
indexnetworkindexnetwork
130

commit-changes

Commit staged code changes in logical chunks using Conventional Commits.

Official
Intermediate