git-commit

Stage changed files, generate commit messages, and confirm before applying git commits.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill git-commit-suniljit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/git-commit
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill git-commit-suniljit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork in assembling meaningful git commits by coordinating what to include, how to describe changes, and when to apply them.

Core Features & Use Cases

  • Stage changes based on user input or repository status.
  • Generate clear, conventional commit messages aligned with project guidelines.
  • Confirm with the user before applying the commit to ensure safety and accuracy.

Quick Start

Ask me to stage the changes you want and prepare a commit message, then confirm to 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 conventional commit messages for changed git files?

To generate conventional commit messages, this skill analyzes your changed files and user intent to produce clear, guideline-aligned messages. It coordinates staging, message generation, and user confirmation before applying the commit.

Can I review a git commit message before it is applied to the repository?

Yes, you can review the commit message before application. The workflow enforces a mandatory user confirmation step after message generation to ensure safety and accuracy before staging and committing changes.

What is the best way to automate staging specific files in a git workflow?

Automating git staging involves specifying target files to the workflow, which analyzes the repository status and user input to stage changes. This controlled flow ensures only intended files are included in the commit.

Does git-commit work without external dependencies or component installations?

Yes, git-commit operates without external dependencies or component installations. It functions as an advanced standalone skill to coordinate version-control tasks directly through its internal multi-step reasoning workflow.

Why should I use a multi-step workflow for version-control commits?

A multi-step workflow for version-control commits prevents unintended changes by separating discovery, message generation, and application. This controlled process ensures codebase accuracy and enforces user confirmation before finalizing the commit.

How do I prepare a codebase commit when I only have a general intent for the changes?

Preparing a codebase commit with general intent requires the skill to analyze repository status and changed files, generate a matching conventional message, and prompt for user confirmation to safely apply the commit.