Commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
Install
/plugin marketplace add sneg55/agent-starterThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sneg55/agent-starter --skill commitgit clone --depth 1 https://github.com/sneg55/agent-starter.git /tmp/agent-starter
mkdir -p ~/.claude/skills
cp -r /tmp/agent-starter/skills/commit ~/.claude/skills/commitPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Git 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: 1. 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.)
Details
- Skill name
commit- Repository
- sneg55/agent-starter
- Path
skills/commit/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Commit skill do?
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
How do I install the Commit skill?
Claude Code plugin: /plugin marketplace add sneg55/agent-starter. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Commit popular?
It lives in sneg55/agent-starter, which has 75 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adopt Project
75sneg55/agent-starter
Apply agent-starter patterns to an EXISTING project - audits the codebase, proposes components by invasiveness tier (hooks, skills, CLAUDE.md, lint configs, patterns), and applies only what the developer approves. Use when the user says adopt, retrofit, "apply agent-starter to this project", or wants starter patterns in an existing codebase.
Commit Push PR
75sneg55/agent-starter
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
Dream
75sneg55/agent-starter
Memory consolidation - review, merge, prune, and index memory files. Run periodically to keep memories organized and up-to-date.
GitLab Stack Validator
93rknall/claude-skills
Validates GitLab stack projects before deployment, ensuring proper architecture patterns, directory structure, secrets management, .env configuration, and Docker best practices. Use when users ask to validate a stack, check stack configuration, verify stack architecture, audit stack setup, or ensure stack deployment readiness.
Clab
54mberneti/clab
AI-powered review of self-hosted GitLab merge requests. Fetches MR diff, applies project-specific rules, posts inline comments. Can analyze past MRs to generate review rules.
GitLab Stack Secrets Manager
93rknall/claude-skills
Manages Docker secrets for GitLab stack projects, ensuring secrets are never in .env or docker-compose.yml, properly stored in ./secrets directory, and securely integrated with Docker secrets. Use when users need to create secrets, migrate from environment variables, validate secret configuration, audit secret usage, or ensure secrets are never committed to git.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.