/commit and /commit-push-pr — Claude Code git skills that write real commit messages

commit-skill.md

/commit and /commit-push-pr — Claude Code Git Skills

Two custom slash commands that make Claude write your git commit messages and open pull requests automatically.

---

Install

1. Create the folder: mkdir -p .claude/plugins/commit-commands/commands
2. Add the two files below
3. In Claude Code, run: /commit or /commit-push-pr

---

File 1: .claude/plugins/commit-commands/commands/commit.md

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: Create a git commit
---

## Context

- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -10`

## Your task

Based on the above changes, create a single git commit.

You have the capability to call multiple tools in a single response.
Stage and create the commit using a single message.
Do not use any other tools or do anything else.
Do not send any other text or messages besides these tool calls.

---

File 2: .claude/plugins/commit-commands/commands/commit-push-pr.md

---
allowed-tools: Bash(git checkout --branch:*), Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*), Bash(gh pr create:*)
description: Commit, push, and open a PR
---

## Context

- Current git status: !`git status`
- Current git diff (staged and unstaged changes): !`git diff HEAD`
- Current branch: !`git branch --show-current`

## Your task

Based on the above changes:

1. Create a new branch if on main
2. Create a single commit with an appropriate message
3. Push the branch to origin
4. Create a pull request using `gh pr create`
5. You have the capability to call multiple tools in a single response.
   You MUST do all of the above in a single message.
   Do not use any other tools or do anything else.
   Do not send any other text or messages besides these tool calls.

---

How it works

• /commit — reads your diff, writes a conventional commit message, stages everything, commits
• /commit-push-pr — does the same, then pushes to a branch and opens a GitHub PR with a real description

The commit message Claude writes explains why the change was made, not what the diff already shows.

---

For more Claude Code skills and the complete Operator workflow: → https://get.caffier-agency.com?utm_source=instagram&utm_medium=gist&utm_campaign=GIT