skills.rest
gannonh
gannonhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

committing-changes

Stage files explicitly and create conventional git commit messages.

1|Updated Jun 19, 2026
Search Tags:#git#workflow#commit#staging#commit-message#conventional-commits
One-click install
npx skills add https://github.com/gannonh/kata-agents --skill committing-changes-gannonh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/gannonh/kata-agents/tree/main/skills/committing-changes
Command: npx skills add https://github.com/gannonh/kata-agents --skill committing-changes-gannonh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers ensure their git history is clean and easy to review by guiding explicit file staging and the use of conventional commit messages.

Core Features & Use Cases

  • Explicit staging: Stage only the files you intend to commit.
  • Conventional commits: Enforce standard commit message formats to improve history readability.
  • Guided workflow: Step-by-step prompts to craft appropriate messages for feature, bugfix, or chore commits.
  • Use Case: When preparing a release or reviewing changes across multiple files, generate a clear commit that communicates intent.

Quick Start

Stage the changed files and commit with a conventional message, for example: git add path/to/file git commit -m 'feat(ui): align button layout'

Frequently Asked Questions about committing-changes

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

FAQPage Schema
What is a conventional commit message and when should I use it?▼

A conventional commit message uses a structured format like 'feat(ui): align button layout' to communicate intent. Use conventional commits to improve git history readability and ensure your commit messages are clean and easy to review.

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

To stage specific files for a git commit, use explicit file staging by running 'git add path/to/file'. This ensures you only stage the files you intend to commit, keeping your git history clean and easy to review.

What's the best way to write git commit messages for multiple file changes?▼

The best way to write git commit messages for multiple file changes is to use a guided workflow with step-by-step prompts. This helps you stage files explicitly and craft clear conventional commit messages that communicate intent.

Can I use this guided workflow for feature, bugfix, and chore commits?▼

Yes, the guided workflow provides step-by-step prompts to craft appropriate conventional commit messages for feature, bugfix, or chore commits, ensuring standard commit message formats across your git history.

Do I need any dependencies to enforce conventional commit formats?▼

No dependencies are required. The guided workflow helps you enforce standard conventional commit formats and explicit file staging natively, ensuring a clean git history without additional tools.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
lucidashlucidash
5

open-pr

Create GitHub pull requests from local commits using gh or the GitHub API.

Community
Advanced
dhruvinrsonidhruvinrsoni

release-notes

Parse git history to generate changelogs and release notes.

Community
Advanced
JavierLianoRiozJavierLianoRioz
3

git-commit

Generate conventional Git commit messages from code diffs with intelligent file staging.

Community
Intermediate