Skill

Context

From ox

Commits changes with a short imperative git message following strict style rules; creates new branch if on main. Uses git status, diff, log for context.

Git

git-workflow

npx claudepluginhub oxidian/cc-plugins --plugin ox

Tool Access

This skill is limited to using the following tools:

Bash(git checkout --branch:*)Bash(git checkout -b:*)Bash(git add:*)Bash(git status:*)Bash(git commit:*)Bash(git log:*)

Preview

- Current git status: !`git status`

SKILL.md

Similar Skills

git-commit

13.2k

Creates git commits with clear messages from working tree changes, following repo conventions or conventional commits. Handles clean trees and detached HEAD.

compound-engineering

git-commit

Creates git commits with clear, value-communicating messages from staged or unstaged changes, following repo conventions or conventional commit format. Use when user says 'commit' or 'save changes'.

spec-first

Context

Automates Git workflow: creates new branch if on main, commits changes with short imperative message, pushes to origin, and opens GitHub PR via gh CLI. Use after code changes.

8 tools

oxgh

Stats

Parent Repo Stars11

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Commit style

Use a short commit message (one line, imperative mood) that describes WHAT changed - never meta-messages like "Address review feedback" or "Fix PR comments"
The commit body should usually be blank - the code should speak for itself
ONLY add a body to explain NON-OBVIOUS changes that aren't clear from the code
Do NOT repeat or describe what the code does - that's redundant
Do NOT prepend commit messages with "RED", "GREEN", or other TDD phase labels - just describe the change
See recent commits for examples (ignore dependabot and github-actions commits)

Your task

Based on the above changes:

Create a new branch if on main (do NOT add timestamps to branch names)
Create a single commit with an appropriate message
You have the capability to call multiple tools in a single response. You MUST do the above in a single message using separate tool calls for each command. Do NOT chain commands with && or ;. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.