commit-dis

Stage and commit only conversation-modified files to the current Git branch.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill commit-dis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-dis
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.claude/skills/commit-dis
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill commit-dis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of accidentally committing unrelated files, creating new branches, or pushing changes when you only want to save the work you completed during your current conversation.

Core Features & Use Cases

  • Scoped Staging: Only stages files you explicitly edited in the current session, avoiding overcommit of unrelated working tree changes or build artifacts.
  • Branch Safety: Automatically operates on the currently checked-out branch, never creating, switching, or renaming branches.
  • Use Case: After fixing a login flow bug during a chat session, use this Skill to commit only the login-related file changes to your current feature branch without touching other in-progress work.

Quick Start

Use the commit-dis skill to save all the changes you made to project files during this conversation as a single commit on your current branch.

Frequently Asked Questions about commit-dis

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

FAQPage Schema
How do I commit only the files modified during my current session without staging unrelated working tree changes?

To commit only session files without staging unrelated working tree changes, this Skill enforces strict scoped staging. It identifies explicitly edited files from your current conversation and stages them, avoiding overcommitting build artifacts or other in-progress work.

What is the safest way to save my current chat session work to a Git branch?

The safest way to save current chat session work is to use branch safety mechanisms that commit strictly to the currently checked-out Git branch. This ensures no new branches are created, renamed, or switched to during the scoped commit process.

Can I use this to quickly save session work without pushing changes or opening pull requests?

Yes, you can use this to save session work without pushing changes or opening pull requests. It strictly stages and commits modified conversation files locally, bypassing any remote Git operations or branch management features.

Does this Git commit method avoid creating new branches or switching my current context?

Yes, this Git commit method avoids creating new branches or switching context. It operates automatically on the currently checked-out branch, guaranteeing branch safety and preserving your existing working state without any checkouts.

How do I prevent accidentally committing build artifacts or unrelated in-progress files in version control?

To prevent accidentally committing build artifacts or unrelated files in version control, use scoped staging. This approach only stages files explicitly modified during your current conversation, ignoring all other working tree changes.