commit-changes

Stage only modified files and create a Conventional Commits message.

Updated Feb 26, 2026

Search Tags:#git #commit #staging #conventional-commits #selective-staging

Ready to run

npx skills add https://github.com/heikopanjas/agent-skills --skill commit-changes-heikopanjas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-changes
Source: https://github.com/heikopanjas/agent-skills/tree/main/commit-changes
Command: npx skills add https://github.com/heikopanjas/agent-skills --skill commit-changes-heikopanjas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit only the modified files relevant to a change, preventing unnecessary churn in repository history and making audits easier.

Core Features & Use Cases

Selective staging: Stage only files that relate to the intended change using git add with specific paths, rather than all modified files.
Conventional commits alignment: Enforce conventional commit messages to improve readability and automation.
Use Case: When fixing a bug across a small subset of files, stage those files and produce a precise, conventional commit.

Quick Start

Instruct the AI to stage the relevant files and create a conventional commit for the described change.

Frequently Asked Questions about commit-changes

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

FAQPage Schema

How do I stage only specific modified files for a git commit?▼

To stage only specific modified files for a git commit, use selective staging by running git add with explicit file paths rather than staging all changes. This prevents unnecessary churn and keeps repository history focused on the intended change.

What is a conventional commit and why use it for bug fixes?▼

A conventional commit is a formatted commit message that improves readability and automation. Using it for bug fixes ensures precise history tracing, making code audits easier and clearly communicating the nature of the incremental enhancement.

How do I create a precise git commit for an incremental enhancement?▼

To create a precise git commit for an incremental enhancement, stage only the relevant modified files using specific paths and generate a conventional commit message. This results in a minimal commit that is easier to review.

Can I fix a bug across a small subset of files without staging everything?▼

Yes, you can fix a bug across a small subset of files without staging everything by using selective staging. Apply git add to only the relevant paths to produce a precise, conventional commit without unrelated churn.

What is the best way to enforce conventional commit messages in a repository?▼

The best way to enforce conventional commit messages is to align staging with the intended change and generate messages following the Conventional Commits format. This improves repository readability and supports history tracing automation.