skills.rest
wangrenzhu-ola
wangrenzhu-olaCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Create a git commit with a conventional commit message from staged or unstaged changes.

2|1|Updated Apr 17, 2026
Search Tags:#git#workflow#commit#codebase#changes#version-control#conventional-commits
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill git-commit-wangrenzhu-ola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/git-commit
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill git-commit-wangrenzhu-ola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a git commit from the current working tree changes with a clear, value-oriented message. It ensures the commit follows repository conventions when they exist and defaults to the conventional commit format otherwise.

Core Features & Use Cases

  • Generate a single, well-crafted commit from staged or unstaged changes, aligning with repo conventions if present and falling back to conventional commits.
  • Guide through gathering context (git status, diff, branch, recent commits) and advise safe branching decisions when needed.
  • Ensure the final commit message has a concise subject and an optional body that explains motivation and trade-offs.

Quick Start

Tell me what changed and I will craft and commit a clear, conventional git message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create a git commit that follows conventional commits standard?▼

You can generate a conventional commit by instructing the tool to analyze your staged or unstaged changes. It gathers context from git status and recent commits to craft a message with a concise subject and body, conforming to the conventional commits standard or existing repository conventions.

How do I commit unstaged changes safely without accidentally including unrelated files?▼

To commit unstaged changes safely, the workflow enforces scoped staging by gathering context from git status and diff. It carefully isolates intended changes to ensure only relevant modifications are included in the final commit creation.

Does this workflow generate commit messages based on existing repository conventions?▼

Yes, the workflow generates commit messages based on existing repository conventions. It gathers context from recent commits and branch naming to align with your project standards, falling back to the conventional commit format only when no specific repo conventions are detected.

What is the best way to write a git commit message that explains codebase changes and motivation?▼

The best way to write a git commit message explaining codebase changes is to ensure the final message has a concise subject and an optional body. This process analyzes the working tree diff to explain motivation and trade-offs clearly and value-orientedly.

Can I use this to guide branching decisions before creating a version-control commit?▼

Yes, you can use this to guide branching decisions before creating a version-control commit. The workflow advises safe branching decisions by gathering context from your current git status and branch name before proceeding with scoped staging and commit creation.

Related Skills

Explore More Software Engineering Skills→
sommiosommio
1

git-commit

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

Community
Intermediate
HerrsosaHerrsosa

commit-push

Stage, commit, and push Git changes to the main branch.

Community
Intermediate
julianobarbosajulianobarbosa
7

Commit

Automate Git commits with pre-commit security scans and Conventional Commits enforcement.

Community
Advanced
0xrafasec0xrafasec
9

commit

Stage and commit git changes with conventional commit messages.

Community
Intermediate