Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and…
Install Commit Craft
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craft --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .claude/skills/commit-craft && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .claude/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craftType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craft --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .agents/skills/commit-craft && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .agents/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craft --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .cursor/skills/commit-craft && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .cursor/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ccplugins/awesome-claude-code-plugins.git --path plugins/craftsman/skills/commit-craft--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craft --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .gemini/skills/commit-craft && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .gemini/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craftInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .github/skills/commit-craft && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .github/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins commit-craft --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/craftsman/skills/commit-craft .opencode/skills/commit-craft && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "commit-craft" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/commit-craft into .opencode/skills/commit-craft/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-craft", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
commit-craft- GitHub stars
- 967
- Token cost
- ~1.2k tokens
- SKILL.md length
- 608 words
- Files
- 1
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and…
- Tasks that involve Pull requests
- SKILL.md covers Overview, When this applies, Permission gate (do this first) and Commits, plus 4 more sections
- Calls git; reaches claude.com
- Tasks that involve Commit messages
What it does
Commit Craft is an agent skill from ccplugins/awesome-claude-code-plugins. Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and safe to ship.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests and Commit messages. It works with Git. The repository describes itself as: Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Pull requests
- Tasks that involve Commit messages
Example prompts
- “/commit-craft”
What it can do on your machine
Read from SKILL.md and the folder at commit 5bd4f16. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Commit Craft loads about 1.2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 608 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:53
**Never commit:** secrets, credentials, `.env` files, generated/build artifacts, large binaries, or
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ccplugins/awesome-claude-code-plugins at commit 5bd4f16, republished under its Apache-2.0 licence (© ccplugins). 608 words, ~1,181 tokens.
Download SKILL.mdSave it as
.claude/skills/commit-craft/SKILL.md (or your agent's skills folder).- name
- commit-craft
- description
- Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and safe to ship.
Commit Craft
Overview
Version-control history is documentation that outlives every summary. A commit is read far more often than it's written — during review, bisects, blame, and reverts months later. Sloppy history turns those into archaeology; disciplined history makes them a one-line answer.
Core principle: every commit should be a single, reversible, explainable unit of change.
When this applies
Any time work reaches git: staging a commit, cutting a branch, or opening a PR. Skip it only for throwaway experiments you never intend to keep. It does not depend on any other plugin being installed.
Permission gate (do this first)
- Only commit, push, or open a PR when the user asks. Finishing a code change is not implicit permission to commit it — surface the diff and let them decide.
- Never commit directly to the default branch without asking. If the current branch is
main/masterand the user hasn't said otherwise, branch first (see naming below), then commit. - Never use
--no-verify,--no-gpg-sign, or skip hooks unless the user explicitly asks. A failing hook is a signal to fix, not to bypass.
Commits
Atomic. One logical change per commit. Don't mix a refactor with a feature, or a formatting
sweep with a bug fix — a reviewer (and a future git revert) should be able to take or drop the
change as a whole. Split unrelated work into separate commits.
Message format:
<imperative subject, ~50 chars, no trailing period>
<body: wrap ~72 chars. Explain WHY the change is needed and what it
affects — the diff already shows what changed. Reference issues/PRs.>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>- Subject in the imperative mood: "Add retry to uploader", not "Added" / "Adds" / "Fixing".
- Body is optional for genuinely trivial commits, required when the why isn't obvious from the subject. Prefer prose that answers "why now / why this way" over restating the diff.
- End the message with the
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>trailer.
Never commit: secrets, credentials, .env files, generated/build artifacts, large binaries, or
anything already ignored. If git status shows something that should be ignored, fix .gitignore
first — don't commit it "just this once."
Branches
Name branches <type>/<short-kebab-summary>, using the same type vocabulary as commits/PRs:
feat/— new capability ·fix/— bug fix ·chore/— tooling, deps, configdocs/— documentation ·refactor/— behavior-preserving restructure
Examples: feat/search-filters, fix/quiz-empty-wordlist, chore/pin-actions-sha.
Show full SKILL.md (268 more words)Show less
History hygiene
- Squash fixup noise ("wip", "typo", "address review") before merging, so each landed commit is meaningful and the branch stays bisectable.
- Rebase your own unpushed local branch to keep history linear; never rebase or force-push a
branch others may have pulled. If you must update a shared branch, prefer
--force-with-leaseover--force, and only when the user has agreed. - Prefer a new commit over amending a commit that's already pushed.
Pull requests
Small and focused beats large and sweeping — easier to review, safer to revert.
Title: same imperative style as a commit subject.
Body: what changed and why, how it was tested/verified, and links to any issue it closes (
Closes #123). End the PR body with:🤖 Generated with [Claude Code](https://claude.com/claude-code)Green before merge: the most recent CI run on the branch must pass. Don't merge red, and don't disable a check to go green.
Reference PRs/issues as full markdown links, never a bare
#123.
Red flags
| Thought | Reality |
|---|---|
| "I finished the change, so I'll just commit it" | Completing work isn't permission to commit. Ask first. |
| "I'll bundle these three unrelated fixes into one commit" | That's not atomic — split them so each can be reverted alone. |
| "The subject says it all, skip the body" | Fine only if why is obvious. If it isn't, the body is where it belongs. |
| "I'm on main but it's a tiny change" | Branch first. Size doesn't change the rule. |
"The hook is failing, I'll add --no-verify" | The hook caught something. Fix it, don't bypass it. |
| "I'll force-push to clean up the shared branch" | You may clobber someone's work. --force-with-lease, and only with agreement. |
© ccplugins, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/craftsman/skills/commit-craft of ccplugins/awesome-claude-code-plugins.
Open the folder on GitHubat commit 5bd4f16
Compare with similar skills
Commit Craft next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Commit Craft this skillccplugins/awesome-claude-code-plugins | 967 | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 |
Similar skills
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
Submit PR
tisfeng/Easydict
创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。
More from ccplugins/awesome-claude-code-plugins
All 68 skills in this repoAI Meeting
ccplugins/awesome-claude-code-plugins
Run structured AI meetings for plans, product ideas, technical designs, business decisions, feature proposals, and strategy choices.
Fastapi App
ccplugins/awesome-claude-code-plugins
Bootstrap a new FastAPI backend with async SQLAlchemy 2.0, asyncpg, Alembic, Pydantic v2, and no deprecated APIs.
Flutter App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs.
Nextjs App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Next.js (App Router, TypeScript) web app with current packages and no deprecated APIs.
Dev Report
ccplugins/awesome-claude-code-plugins
Write up a coding session for a non-technical stakeholder — the context, what was built, and the engineering reasoning behind it — the way a senior engineer briefs a product manager who does not…
Difesa Attacchi
ccplugins/awesome-claude-code-plugins
Aggiunge a un sito/app un agente di difesa che rileva e blocca richieste malevole (SQL injection, XSS, path traversal, brute force, bot) con rate limiting, blocklist IP e modalità lockdown che…
Related
Works with
Categories
Questions about Commit Craft
What does Commit Craft do?
Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and…. Commit Craft is an agent skill from ccplugins/awesome-claude-code-plugins. Use before any git commit, branch, or pull request — defines the project's conventions for atomic commits, message format, branch naming, and PR hygiene so history stays navigable, bisectable, and safe to ship.
When should I use Commit Craft?
Commit Craft fits situations like: tasks that involve Pull requests; tasks that involve Commit messages.
How do I install Commit Craft in Claude Code?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a claude-code`. Or copy the skill folder (plugins/craftsman/skills/commit-craft in ccplugins/awesome-claude-code-plugins) into .claude/skills/commit-craft in your project. Claude Code loads it when a task matches its description.
How do I install Commit Craft in Codex?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a codex`. Or copy the skill folder (plugins/craftsman/skills/commit-craft in ccplugins/awesome-claude-code-plugins) into .agents/skills/commit-craft in your project. Codex loads it when a task matches its description.
Can I use Commit Craft in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ccplugins/awesome-claude-code-plugins --skill commit-craft -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-craft, .gemini/skills/commit-craft, .github/skills/commit-craft and .opencode/skills/commit-craft in your project.
What does Commit Craft need to run?
Going by SKILL.md and its folder, Commit Craft needs the command-line tools its instructions call (git).
Does Commit Craft access the network?
SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Commit Craft safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Commit Craft use?
Commit Craft is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Commit Craft use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Commit Craft?
Skills that share tags, products or a category with Commit Craft: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commit Craft?
ccplugins (a GitHub organization) maintains it in ccplugins/awesome-claude-code-plugins, which has 967 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on August 12, 2026.
Source: ccplugins/awesome-claude-code-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.