commit

Stage and commit only files discussed in the conversation.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/yoshihiko555/dotfiles --skill commit-yoshihiko555
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/yoshihiko555/dotfiles/tree/main/shared/skills/common/commit
Command: npx skills add https://github.com/yoshihiko555/dotfiles --skill commit-yoshihiko555

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a single, context-aware git commit from the current conversation changes.

Core Features & Use Cases

  • Context-aware staging: only include files discussed in the chat.
  • Granular staging: add each relevant file individually with git add <path>.
  • One-commit guarantee: produce a single commit describing all changes succinctly.

Quick Start

Ask the AI to stage only the files discussed and create one commit describing the changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git commit for only the files discussed in my current conversation?

To create a git commit for only the files discussed, this Skill stages each relevant file individually with git add and generates a single commit, ignoring unrelated modifications in your working directory.

What is context-aware git commit generation?

Context-aware git commit generation limits the staging scope to files directly touched in your current conversation, ensuring the final commit only includes relevant changes rather than all working directory modifications.

How do I stage specific files individually before creating a single commit?

You can stage specific files individually by instructing the AI to scope changes to the current chat, which triggers granular git add commands for each file before producing one unified commit.

Can I generate a single git commit for multiple files modified during an AI chat session?

Yes, you can generate a single git commit for multiple files by asking the AI to stage only the discussed files, which guarantees one commit describing all changes succinctly without including unrelated edits.

Why does my git commit include unrelated changes from the working directory?

Your git commit includes unrelated changes because standard staging captures all modified files, whereas this context-aware approach restricts staging to only files touched in the current conversation.

Are there limitations to using context-aware staging for version control?

A limitation of context-aware staging is that it only processes files explicitly discussed in the current conversation, meaning any unrelated working directory changes must be committed separately.