commit

Stage session-touched files and create local Git commits with git commit -F.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/donygeorge/claude-toolkit --skill commit-donygeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/donygeorge/claude-toolkit/tree/main/skills/commit
Command: npx skills add https://github.com/donygeorge/claude-toolkit --skill commit-donygeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically constrain commits to files touched during the current Claude Code session, preventing accidental inclusion of unrelated changes.

Core Features & Use Cases

  • Session-aware staging: analyzes git status and conversation history to select session files.
  • Safe commit messaging: writes messages to a temp file and uses git commit -F to avoid shell escaping issues.
  • Guardrails: prevents bulk adds, pushes, amend, or force pushes; ensures local-only commits.

Quick Start

Commit only the files touched in this Claude Code session, staging them individually and creating a descriptive local commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit only the files modified in my current coding session?

Session-aware staging analyzes git status and conversation history to select only files touched during the current Claude Code session. It stages them individually and creates a descriptive local commit, preventing accidental inclusion of unrelated changes.

What is the safest way to write a git commit message without shell escaping issues?

Safe commit messaging writes the message to a temp file and uses git commit -F to avoid shell escaping issues entirely. This ensures the commit message is preserved exactly as intended in the local version control history.

How do I prevent accidental bulk git adds or force pushes when staging changes?

Built-in guardrails prevent bulk adds, pushes, amend, and force pushes by constraining commits to session-touched files only. These safety measures ensure local-only commits and protect project history integrity.

Can I use this to stage specific files for version control without pushing to remote?

Yes, you can stage specific files without pushing to remote. The Skill relies on git status checks to identify session changes and explicitly prohibits pushes, ensuring all commits remain strictly local for safe version control.

When should I not use an automated session-aware git commit workflow?

You should avoid this workflow if you need to amend previous commits, force push, or stage files outside the current session. Its guardrails prohibit history rewrites and remote operations to protect project integrity.