How do I install the Commit Dis skill?

Run npx skillmds@latest add kortix-ai/commit-dis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit Dis safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Dis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Dis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Dis?

kortix-ai (@kortix-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Dis by kortix-ai — Agent Skill

Name: Commit Dis
Rating: 4.666666666666667 (3 reviews)
Author: kortix-ai

Commit Dis

Stage and commit ONLY the work done in this session, on the CURRENT branch — no new branch, no PR, no push. Load whenever the user says 'commit this', 'commit-dis', 'git add commit what we did', 'commit dis', 'save my work', or otherwise asks to commit the changes from the current thread. Enforces: stay on the already-checked-out branch, never overcommit unrelated files.

kortix-ai Updated Sep 10, 2026

File contents

commit-dis — commit this session's work, here, now

Stage and commit the changes produced during this conversation onto the current branch. Nothing more. This is the quick "save what we just did" button.

THE RULES

Stay on the current branch. Do NOT create, switch, or rename a branch. Commit wherever HEAD already points — even if that's main. Never run git checkout -b, git switch -c, or git branch.
Only commit what this session changed. Stage the specific files you created or edited in this thread by path. Do NOT git add -A / git add . blindly — that risks sweeping in unrelated working-tree changes, untracked scratch files, or another task's edits. No overcommitting.
No push, no PR. Stop after the commit unless the user explicitly asks to push or open a PR.
One commit for the session's work unless the user asks otherwise.

Steps

Confirm the branch and see what's changed:

git rev-parse --abbrev-ref HEAD
git status --short

Identify the exact files this session touched. If anything in git status was NOT changed by this session, leave it unstaged. If it's ambiguous whether a dirty file belongs to this session, ask the user rather than guessing.
Stage by explicit path (never -A/.):
```
git add <file1> <file2> ...
```
Commit with a clear message describing what this session did. End the message with the standard trailer:
```
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
```
Confirm:
```
git log --oneline -1
```

Don't

Don't create or switch branches.
Don't git add -A, git add ., or git commit -a.
Don't push or open a PR.
Don't amend or rebase prior commits.
Don't stage files you didn't touch this session (build artifacts, other in-flight work, untracked scratch).

---name: commit-disdescription: Stage and commit ONLY the work done in this session, on the CURRENT branch — no new branch, no PR, no push. Load whenever the user says 'commit this', 'commit-dis', 'git add commit what we did', 'commit dis', 'save my work', or otherwise asks to commit the changes from the current thread. Enforces: stay on the already-checked-out branch, never overcommit unrelated files.---# commit-dis — commit this session's work, here, nowStage and commit the changes produced during **this conversation** onto the**current branch**. Nothing more. This is the quick "save what we just did"button.## THE RULES1. **Stay on the current branch.** Do NOT create, switch, or rename a branch. Commit wherever `HEAD` already points — even if that's `main`. Never run `git checkout -b`, `git switch -c`, or `git branch`.2. **Only commit what this session changed.** Stage the specific files you created or edited in this thread by path. Do NOT `git add -A` / `git add .` blindly — that risks sweeping in unrelated working-tree changes, untracked scratch files, or another task's edits. No overcommitting.3. **No push, no PR.** Stop after the commit unless the user explicitly asks to push or open a PR.4. **One commit** for the session's work unless the user asks otherwise.## Steps1. Confirm the branch and see what's changed: ```bash git rev-parse --abbrev-ref HEAD git status --short ```2. Identify the exact files **this session** touched. If anything in `git status` was NOT changed by this session, leave it unstaged. If it's ambiguous whether a dirty file belongs to this session, ask the user rather than guessing.3. Stage by explicit path (never `-A`/`.`): ```bash git add <file1> <file2> ... ```4. Commit with a clear message describing what this session did. End the message with the standard trailer: ``` Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> ```5. Confirm: ```bash git log --oneline -1 ```## Don't- Don't create or switch branches.- Don't `git add -A`, `git add .`, or `git commit -a`.- Don't push or open a PR.- Don't amend or rebase prior commits.- Don't stage files you didn't touch this session (build artifacts, other in-flight work, untracked scratch).

Frequently asked questions