Git Commit Pro
Write well-structured git commit messages following the Conventional Commits standard. Use when a user asks to commit changes, write a commit message, stage and commit, improve a commit message, or follow commit conventions. Analyzes diffs to produce accurate, meaningful commit messages.
Install
npx skills add TerminalSkills/skills --skill git-commit-progit clone --depth 1 https://github.com/TerminalSkills/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/git-commit-pro ~/.claude/skills/git-commit-proPersonal 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 Pro ## Overview Generate well-structured git commit messages by analyzing staged changes. Follows Conventional Commits format and produces messages that explain what changed and why. ## Instructions When a user asks you to commit, write a commit message, or improve an existing commit message, follow these steps: ### Step 1: Inspect the changes ```bash # See what is staged git diff --cached --stat # See full staged diff git diff --cached # See unstaged changes (in case user wants to stage first) git status ``` If nothing is staged, help the user stage the right files first. Never use `git add .` unless the user explicitly asks -- prefer adding specific files. ### Step 2: Analyze the diff Categorize what changed: - **New files**: What functionality do they add? - **Modified files**: What behavior changed? Why? - **Deleted files**: What was removed and why? - **Renamed/moved files**: What restructuring happened? Look at the actual code changes, not just file names. Understand the intent behind the changes. ### Step 3: Write the commit message Use Conventional Commits format: ``` type(scope): short description Longer explanation of what changed and why. Wrap at 72 characters. Reference any issues or tickets. BREAKING CHANGE: description of the incompatible change and what callers must do ```
Details
- Skill name
git-commit-pro- Repository
- TerminalSkills/skills
- Path
skills/git-commit-pro/SKILL.md- License
- Apache-2.0
- Repo updated
- 8 November 2026
FAQ
What does the Git Commit Pro skill do?
Write well-structured git commit messages following the Conventional Commits standard. Use when a user asks to commit changes, write a commit message, stage and commit, improve a commit message, or follow commit conventions. Analyzes diffs to produce accurate, meaningful commit messages.
How do I install the Git Commit Pro skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TerminalSkills/skills --skill git-commit-pro. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git Commit Pro popular?
It lives in TerminalSkills/skills, which has 213 GitHub stars and 34 forks.
Related skills
3dsmax Rendering
213TerminalSkills/skills
Scripts and configures production rendering in Autodesk 3ds Max with the V-Ray and Corona renderers: output size and files, render elements, denoising, light mix, batch and command-line rendering, and network rendering. Use when a user asks to set up a production render, render several cameras in one batch, render from the command line or on a render farm, add render passes for compositing, or cut render time for archviz and product shots.
3dsmax Scripting
213TerminalSkills/skills
Covers scripting Autodesk 3ds Max, the 3D modeling and rendering application, with MAXScript and Python (pymxs): scene manipulation, object creation, material assignment, camera and light setup, batch operations, and file I/O. Use when tasks involve automating repetitive 3ds Max workflows, batch processing scenes, running scripts headless with 3dsmaxbatch, creating custom tools, or scripting scene setup for archviz, product visualization, or VFX.
3proxy
213TerminalSkills/skills
3proxy is a small open-source proxy server that runs HTTP/HTTPS, SOCKS4/5, SNI and TCP/UDP port-mapping proxies from one config file. Use when a user asks to set up an HTTP or SOCKS5 proxy, add proxy users and passwords, write 3proxy access rules, chain or rotate upstream (parent) proxies, limit bandwidth, connections or monthly traffic per user, run 3proxy in Docker, or fix a 3proxy.cfg that will not start.
Git Guardrails Claude Code
213TerminalSkills/skills
Installs a Claude Code PreToolUse hook that stops destructive git commands before the shell runs them: force pushes, pushes to protected branches, reset --hard, clean -f, checkouts and restores that discard edits, stash clear and history rewrites, while risky but legitimate commands become a confirmation prompt. Use when someone says "stop Claude from pushing", "block git push --force", "protect main from Claude Code", "add git safety hooks", "Claude wiped my changes with reset --hard", or wants guardrails before running Claude Code in auto mode or with permissions bypassed.
Commitlint
213TerminalSkills/skills
commitlint checks that Git commit messages follow the Conventional Commits format (type(scope): subject) and fails when they do not. Use when a user asks to standardize commit messages, enforce commit conventions with a husky commit-msg hook, lint commits or PR commits in CI, customize rules, or prepare commits for automated changelogs and semantic versioning.
Github
213TerminalSkills/skills
Interact with GitHub using the gh CLI. Create issues, open pull requests, check CI status, review PRs, manage releases, and run advanced queries. Use when a user asks to create a GitHub issue, open a PR, check CI runs, list pull requests, review a PR, search GitHub issues, or manage releases.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.