commit Skill
Generates well-crafted git commit messages by analyzing diffs and following existing repository styles.
- GitHub Stars
- 75
- Dateien
- 1
- Letzter Commit
- 14. Sept. 2026
- Lizenz
- MIT
- Erlaubte Tools
- 3
Was macht der commit Skill?
commit ist ein Agent Skill. Generates well-crafted git commit messages by analyzing diffs and following existing repository styles.
Zusammenfassung erzeugt aus der SKILL.md des Skills.
Über den commit skill
Writing descriptive git commit messages that explain the purpose of code changes is what this skill automates for developers. When an agent needs to finalize a task, it loads this skill to analyze staged and unstaged diffs alongside recent repository history. By examining the last ten commits, the agent learns the specific formatting style used by the project to ensure consistency across the codebase.
The tool uses bash commands like git status, git diff HEAD, and git branch to gather context before drafting a message. It focuses on the reasoning behind a change rather than just listing the modified files. The process concludes by staging relevant files and executing a git commit command using heredoc syntax. To maintain repository integrity, the skill avoids interactive flags, refuses to amend existing commits without permission, and skips files that appear to contain secrets like .env or credentials.json.
Was ein agent damit machen kann
- 1Automate descriptive commit messagesAsk the agent to create a commit message that explains the reasoning behind your recent code changes.
- 2Maintain repository style consistencyHave the agent write commits that match the existing formatting and tone of your project history.
- 3Secure file stagingEnsure that sensitive configuration files are not accidentally included in your version control history.
Geschrieben basierend auf dem SKILL.md des skills. Jeder use case wurde gegen ein zitat daraus geprüft.
So installierst du den commit Skill
Jeder Befehl kopiert den Skill-Ordner in das Skills-Verzeichnis des Clients. Starte den Client neu oder beginne eine neue Session, um ihn zu laden.Den commit Skill in Plugin installieren
/plugin marketplace add sneg55/agent-starter /plugin install agent-starter@agent-starter
Den commit Skill in Claude Code installieren
~/.claude/skills/commit/SKILL.md
$ npx degit sneg55/agent-starter/skills/commit ~/.claude/skills/commitDen commit Skill in Claude Code (project) installieren
.claude/skills/commit/SKILL.md
$ npx degit sneg55/agent-starter/skills/commit .claude/skills/commitDen commit Skill in Codex installieren
~/.agents/skills/commit/SKILL.md
$ npx degit sneg55/agent-starter/skills/commit ~/.agents/skills/commitDen commit Skill in Gemini CLI installieren
~/.gemini/skills/commit/SKILL.md
$ npx degit sneg55/agent-starter/skills/commit ~/.gemini/skills/commitDen commit Skill in Claude.ai installieren
npx degit sneg55/agent-starter/skills/commit commit && zip -r commit.zip commit # claude.ai → Customize → Skills → + → Create skill → Upload a skill → commit.zip
SKILL.md
Auf GitHub ansehenGit Commit
Context
Gather this context before committing:
- Current git status:
git status - Current git diff (staged and unstaged):
git diff HEAD - Current branch:
git branch --show-current - Recent commits:
git log --oneline -10
Git Safety Protocol
- NEVER update the git config
- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
- CRITICAL: ALWAYS create NEW commits. NEVER use git commit --amend, unless the user explicitly requests it
- Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
Task
Based on the changes, create a single git commit:
-
Analyze all staged changes and draft a commit message:
- Look at the recent commits to follow this repository's commit message style
- Summarize the nature of the changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
- Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.)
- Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-
Stage relevant files and create the commit using HEREDOC syntax:
git commit -m "$(cat <<'EOF'
Commit message here.
EOF
)"
Stage and create the commit in a single message. Do not do anything else.
Dateien in diesem Skill
1commit Skill-Fragen
Wie installiere ich den commit Skill in Claude Code?
Führe npx degit sneg55/agent-starter/skills/commit ~/.claude/skills/commit aus. Claude Code lädt Skills aus ~/.claude/skills (alle Projekte) oder .claude/skills (ein Projekt) und nutzt einen Skill, wenn seine Beschreibung zur Aufgabe passt.
Welche Clients können den commit Skill nutzen?
Jeder Client, der das Agent Skills-Format liest: Claude Code, Codex, Gemini CLI und claude.ai (als ZIP hochladen). Skripte im Skill laufen nur dort, wo der Client Codeausführung erlaubt.
How does the agent decide on the commit message style?
The agent analyzes recent commits in the repository to ensure the new message follows the established commit message style.
Will the agent amend existing commits?
No, the agent is instructed to always create new commits and never use git commit --amend unless explicitly requested by the user.
What happens if there are no changes to commit?
The agent will not create an empty commit if there are no untracked files or modifications.