PR Finalize Review
microsoft/garnet
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
A skill your agent uses when writing git commit messages in this repository.
Install Conventional Commits
$ npx skills add awattar/claude-code-best-practices --skill conventional-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install awattar/claude-code-best-practices conventional-commits --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/awattar/claude-code-best-practices.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/conventional-commits .claude/skills/conventional-commits && 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 "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .claude/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commitsType 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 awattar/claude-code-best-practices --skill conventional-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install awattar/claude-code-best-practices conventional-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awattar/claude-code-best-practices.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/conventional-commits .agents/skills/conventional-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .agents/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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 awattar/claude-code-best-practices --skill conventional-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install awattar/claude-code-best-practices conventional-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awattar/claude-code-best-practices.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/conventional-commits .cursor/skills/conventional-commits && 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 "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .cursor/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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/awattar/claude-code-best-practices.git --path .claude/skills/conventional-commits--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 awattar/claude-code-best-practices --skill conventional-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install awattar/claude-code-best-practices conventional-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awattar/claude-code-best-practices.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/conventional-commits .gemini/skills/conventional-commits && 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 "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .gemini/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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 awattar/claude-code-best-practices conventional-commitsInstalls 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 awattar/claude-code-best-practices --skill conventional-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/awattar/claude-code-best-practices.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/conventional-commits .github/skills/conventional-commits && 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 "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .github/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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 awattar/claude-code-best-practices --skill conventional-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install awattar/claude-code-best-practices conventional-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awattar/claude-code-best-practices.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/conventional-commits .opencode/skills/conventional-commits && 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 "conventional-commits" agent skill from https://github.com/awattar/claude-code-best-practices/tree/main/.claude/skills/conventional-commits into .opencode/skills/conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-commits", 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
conventional-commits- GitHub stars
- 263
- Token cost
- ~395 tokens
- SKILL.md length
- 157 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing git commit messages in this repository.
- Writing git commit messages in this repository
- SKILL.md covers Format, Rules and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Commit messages
What it does
Conventional Commits is an agent skill from awattar/claude-code-best-practices. Use when writing git commit messages in this repository. Enforces the project's conventional commit format — type prefix, GitHub issue reference, and atomic commits — as defined in .gitmessage and .github/COMMITCONVENTION.md.
Its SKILL.md is about 400 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 Commit messages. It works with GitHub. The repository describes itself as: 💻 Best practices and examples for using Claude Code - Anthropic’s terminal-native AI - for writing, editing, and refactoring code with deep project awareness, prompt design, and… The licence is MIT.
When your agent uses it
- Writing git commit messages in this repository
- Tasks that involve Commit messages
Example prompts
- “/conventional-commits”
What it can do on your machine
Read from SKILL.md and the folder at commit 3456a85. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Conventional Commits loads about 395 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 157 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 passed
The automated check found no risky patterns in SKILL.md.
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 awattar/claude-code-best-practices at commit 3456a85, republished under its MIT licence (© awattar). 157 words, ~395 tokens.
Download SKILL.mdSave it as
.claude/skills/conventional-commits/SKILL.md (or your agent's skills folder).- name
- conventional-commits
- description
- Use when writing git commit messages in this repository. Enforces the project's conventional commit format — type prefix, GitHub issue reference, and atomic commits — as defined in .gitmessage and .github/COMMIT_CONVENTION.md.
Conventional Commits
When creating any git commit in this repository, follow the project's commit convention.
Unlike the /commit command (which the user invokes explicitly), this skill applies
automatically whenever a commit message is being authored.
Format
Single-line, when a GitHub issue applies:
<type>: (#<issue_number>) <issue_name> - <description>.Single-line, when no GitHub issue applies:
<type>: <description>.Multiline, when the change spans multiple concerns:
<type>: (#<issue_number>) <issue_name>:
- <description_line_1>.
- <description_line_2>.Rules
<type>is exactly one of:New feature,Fix issue,Other.- Single-line messages end with
.; the first line of a multiline message ends with:. - Every bullet starts with
-and ends with.. - Use present tense, imperative mood ("add feature", not "added feature").
- Keep commits atomic — one logical concern per commit. Split unrelated changes into separate commits.
- NEVER add trailers such as "Generated with Claude Code", author info, or co-author lines.
References
- Full template with examples:
.gitmessage - Commit-splitting guidance and workflow integration:
.github/COMMIT_CONVENTION.md - For an interactive, guided commit flow, use the
/commitcommand.
© awattar, MIT. 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 .claude/skills/conventional-commits of awattar/claude-code-best-practices.
Open the folder on GitHubat commit 3456a85
Compare with similar skills
Conventional Commits 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 |
|---|---|---|---|---|---|---|
| Conventional Commits this skillawattar/claude-code-best-practices | 263 | — | ~395 | Automated safety check: Pass | MIT | |
| PR Finalize Reviewmicrosoft/garnet | 12k | — | ~3.1k | Automated safety check: Pass | 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 | |
| Gh PR Metadatamodule-federation/core | 2.7k | — | ~1k | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 |
Similar skills
- Official
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.
Gh PR Metadata
module-federation/core
Update the current GitHub PR title and body for this repository so they match the repo's pull request template and conventional-commit title style.
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。
Related
Works with
Categories
Questions about Conventional Commits
What does Conventional Commits do?
A skill your agent uses when writing git commit messages in this repository. Conventional Commits is an agent skill from awattar/claude-code-best-practices. Use when writing git commit messages in this repository.
When should I use Conventional Commits?
Conventional Commits fits situations like: writing git commit messages in this repository; tasks that involve Commit messages.
How do I install Conventional Commits in Claude Code?
Run `npx skills add awattar/claude-code-best-practices --skill conventional-commits -a claude-code`. Or copy the skill folder (.claude/skills/conventional-commits in awattar/claude-code-best-practices) into .claude/skills/conventional-commits in your project. Claude Code loads it when a task matches its description.
How do I install Conventional Commits in Codex?
Run `npx skills add awattar/claude-code-best-practices --skill conventional-commits -a codex`. Or copy the skill folder (.claude/skills/conventional-commits in awattar/claude-code-best-practices) into .agents/skills/conventional-commits in your project. Codex loads it when a task matches its description.
Can I use Conventional Commits 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 awattar/claude-code-best-practices --skill conventional-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conventional-commits, .gemini/skills/conventional-commits, .github/skills/conventional-commits and .opencode/skills/conventional-commits in your project.
What does Conventional Commits need to run?
SKILL.md names no scripts, command-line tools or credentials: Conventional Commits is instructions for the agent only.
Does Conventional Commits access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Conventional Commits safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conventional Commits use?
Conventional Commits is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conventional Commits use?
About 395 tokens (SKILL.md is roughly 1.6k 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 Conventional Commits?
Skills that share tags, products or a category with Conventional Commits: PR Finalize Review (microsoft/garnet, 12k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Gh PR Metadata (module-federation/core, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventional Commits?
awattar (a GitHub user) maintains it in awattar/claude-code-best-practices, which has 263 GitHub stars. The repository was last updated on May 22, 2026.
Source: awattar/claude-code-best-practices on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.