skills.rest
wangl-cc
wangl-ccCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Analyze repository state and create scoped git commits with conventional messages.

8|1|Updated Mar 9, 2019
Search Tags:#git#workflow#commit#staging#version-control#conventional-commits
One-click install
npx skills add https://github.com/wangl-cc/dotfiles --skill git-commit-wangl-cc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/wangl-cc/dotfiles/tree/main/home/dot_agents/skills/git-commit
Command: npx skills add https://github.com/wangl-cc/dotfiles --skill git-commit-wangl-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users create precise, well-scoped git commits only when explicitly requested, preventing accidental commits.

Core Features & Use Cases

  • Inspect repository state (git status, staged vs. unstaged changes, recent commit messages) to determine what to commit.
  • Match repository style (e.g., Conventional Commits) and group related changes into a single, logical commit.
  • Enforce safety rules to avoid committing when not asked, require explicit user guidance, and produce a clear commit message.

Quick Start

Ask me to create a focused commit for the current changes and I will stage the related files and craft a concise, well-scoped commit 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 well-scoped git commit for grouped changes?▼

To create a well-scoped git commit, you must explicitly request it. The skill analyzes your repository state, stages related files, and groups them into a single logical commit with a message matching your project's conventions.

How does conventional commits workflow handle staged and unstaged files?▼

The conventional commits workflow inspects both staged and unstaged diffs via git status. It aligns with recent commit messages to group related changes, ensuring the final commit message adheres to repository style.

Can I use this to automatically commit and push version control changes?▼

No, you cannot use this to automatically commit and push version control changes. It enforces safety rules by requiring explicit user prompts for every commit and strictly avoids automatic commits or remote pushes.

What is the best way to match repository commit style for staging files?▼

The best way to match repository commit style is to analyze recent commit messages. The skill inspects your recent git history and applies those formatting conventions to craft a concise message for your staged files.

Why does my version control workflow require explicit prompts before committing?▼

Your version control workflow requires explicit prompts to prevent accidental commits. This safety mechanism ensures changes are only committed when specifically requested, avoiding unintended modifications to the repository state.

Related Skills

Explore More Software Engineering Skills→
oprogramadorrealoprogramadorreal
70

commit-message

Generate conventional commit messages from staged, unstaged, and untracked git changes.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

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

Community
Advanced
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic
WarLikeLauxWarLikeLaux
10

commit

Create atomic Git commits with enforced message formatting and pre-commit checks.

Community
Advanced