New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit

by NeoLabHQ in NeoLabHQ/context-engineering-kit

Create well-formatted commits with conventional commit messages and emoji

GPL-3.0Auto-check passedDevelopment

Install Commit

skills CLI
$ npx skills add NeoLabHQ/context-engineering-kit --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeoLabHQ/context-engineering-kit commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeoLabHQ/context-engineering-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.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/

Facts

Skill name
commit
GitHub stars
1.7k
Token cost
~2.2k tokens
SKILL.md length
1,114 words
Files
1
Skills in repo
57
Repo updated
First seen
Licence
GPL-3.0

At a glance

Create well-formatted commits with conventional commit messages and emoji

  • Works in 8 steps: Branch check: Checks if current branch… → Unless specified with --no-verify,… → Checks which files are staged with git… → …
  • Tasks that involve Commit messages
  • SKILL.md covers Instructions, Best Practices for Commits, Guidelines for Splitting Commits and Examples, plus 3 more sections
  • Calls pnpm and git

What it does

Commit is an agent skill from NeoLabHQ/context-engineering-kit. Create well-formatted commits with conventional commit messages and emoji

Its SKILL.md is about 2.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 Commit messages. It works with Git. The repository describes itself as: Hand-crafted Claude Code Skills focused on improving agent results quality. Compatible with OpenCode, Cursor, Antigravity, Gemini CLI, and others. Includes CodeRabbit open-source… The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Commit messages

Example prompts

  • “/commit”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Branch check: Checks if current branch is master or main. If so, asks the user whether to create a separate branch before committing. If…
  2. Unless specified with --no-verify, automatically runs pre-commit checks like pnpm lint or simular depending on the project language.
  3. Checks which files are staged with git status
  4. If 0 files are staged, automatically adds all modified and new files with git add
  5. Performs a git diff to understand what changes are being committed
  6. Analyzes the diff to determine if multiple distinct logical changes are present
  7. If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits
  8. For each commit (or the single commit if not split), creates a commit message using emoji conventional commit format

What it can do on your machine

Read from SKILL.md and the folder at commit 23e2428. 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:

    • pnpm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.

    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 loads about 2.2k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 1,114 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

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 NeoLabHQ/context-engineering-kit at commit 23e2428, republished under its GPL-3.0 licence (© NeoLabHQ). 1,114 words, ~2,165 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).
name
commit
description
Create well-formatted commits with conventional commit messages and emoji

Claude Command: Commit

Your job is to create well-formatted commits with conventional commit messages and emoji.

Instructions

CRITICAL: Perform the following steps exactly as described:

  1. Branch check: Checks if current branch is master or main. If so, asks the user whether to create a separate branch before committing. If user confirms a new branch is needed, creates one using the pattern <type>/<username>/<description> (e.g., feature/leovs09/add-new-command)
  2. Unless specified with --no-verify, automatically runs pre-commit checks like pnpm lint or simular depending on the project language.
  3. Checks which files are staged with git status
  4. If 0 files are staged, automatically adds all modified and new files with git add
  5. Performs a git diff to understand what changes are being committed
  6. Analyzes the diff to determine if multiple distinct logical changes are present
  7. If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits
  8. For each commit (or the single commit if not split), creates a commit message using emoji conventional commit format

Best Practices for Commits

  • Verify before committing: Ensure code is linted, builds correctly, and documentation is updated
  • Atomic commits: Each commit should contain related changes that serve a single purpose
  • Split large changes: If changes touch multiple concerns, split them into separate commits
  • Conventional commit format: Use the format <type>: <description> where type is one of:
    • feat: A new feature
    • fix: A bug fix
    • docs: Documentation changes
    • style: Code style changes (formatting, etc)
    • refactor: Code changes that neither fix bugs nor add features
    • perf: Performance improvements
    • test: Adding or fixing tests
    • chore: Changes to the build process, tools, etc.
  • Present tense, imperative mood: Write commit messages as commands (e.g., "add feature" not "added feature")
  • Concise first line: Keep the first line under 72 characters
  • Emoji: Each commit type is paired with an appropriate emoji:
    • ✨ feat: New feature
    • 🐛 fix: Bug fix
    • 📝 docs: Documentation
    • 💄 style: Formatting/style
    • ♻️ refactor: Code refactoring
    • ⚡️ perf: Performance improvements
    • ✅ test: Tests
    • 🔧 chore: Tooling, configuration
    • 🚀 ci: CI/CD improvements
    • 🗑️ revert: Reverting changes
    • 🧪 test: Add a failing test
    • 🚨 fix: Fix compiler/linter warnings
    • 🔒️ fix: Fix security issues
    • 👥 chore: Add or update contributors
    • 🚚 refactor: Move or rename resources
    • 🏗️ refactor: Make architectural changes
    • 🔀 chore: Merge branches
    • 📦️ chore: Add or update compiled files or packages
    • ➕ chore: Add a dependency
    • ➖ chore: Remove a dependency
    • 🌱 chore: Add or update seed files
    • 🧑💻 chore: Improve developer experience
    • 🧵 feat: Add or update code related to multithreading or concurrency
    • 🔍️ feat: Improve SEO
    • 🏷️ feat: Add or update types
    • 💬 feat: Add or update text and literals
    • 🌐 feat: Internationalization and localization
    • 👔 feat: Add or update business logic
    • 📱 feat: Work on responsive design
    • 🚸 feat: Improve user experience / usability
    • 🩹 fix: Simple fix for a non-critical issue
    • 🥅 fix: Catch errors
    • 👽️ fix: Update code due to external API changes
    • 🔥 fix: Remove code or files
    • 🎨 style: Improve structure/format of the code
    • 🚑️ fix: Critical hotfix
    • 🎉 chore: Begin a project
    • 🔖 chore: Release/Version tags
    • 🚧 wip: Work in progress
    • 💚 fix: Fix CI build
    • 📌 chore: Pin dependencies to specific versions
    • 👷 ci: Add or update CI build system
    • 📈 feat: Add or update analytics or tracking code
    • ✏️ fix: Fix typos
    • ⏪️ revert: Revert changes
    • 📄 chore: Add or update license
    • 💥 feat: Introduce breaking changes
    • 🍱 assets: Add or update assets
    • ♿️ feat: Improve accessibility
    • 💡 docs: Add or update comments in source code
    • 🗃️ db: Perform database related changes
    • 🔊 feat: Add or update logs
    • 🔇 fix: Remove logs
    • 🤡 test: Mock things
    • 🥚 feat: Add or update an easter egg
    • 🙈 chore: Add or update .gitignore file
    • 📸 test: Add or update snapshots
    • ⚗️ experiment: Perform experiments
    • 🚩 feat: Add, update, or remove feature flags
    • 💫 ui: Add or update animations and transitions
    • ⚰️ refactor: Remove dead code
    • 🦺 feat: Add or update code related to validation
    • ✈️ feat: Improve offline support

Guidelines for Splitting Commits

When analyzing the diff, consider splitting commits based on these criteria:

  1. Different concerns: Changes to unrelated parts of the codebase
  2. Different types of changes: Mixing features, fixes, refactoring, etc.
  3. File patterns: Changes to different types of files (e.g., source code vs documentation)
  4. Logical grouping: Changes that would be easier to understand or review separately
  5. Size: Very large changes that would be clearer if broken down
Show full SKILL.md (443 more words)Show less

Examples

Good commit messages:

  • ✨ feat: add user authentication system
  • 🐛 fix: resolve memory leak in rendering process
  • 📝 docs: update API documentation with new endpoints
  • ♻️ refactor: simplify error handling logic in parser
  • 🚨 fix: resolve linter warnings in component files
  • 🧑💻 chore: improve developer tooling setup process
  • 👔 feat: implement business logic for transaction validation
  • 🩹 fix: address minor styling inconsistency in header
  • 🚑️ fix: patch critical security vulnerability in auth flow
  • 🎨 style: reorganize component structure for better readability
  • 🔥 fix: remove deprecated legacy code
  • 🦺 feat: add input validation for user registration form
  • 💚 fix: resolve failing CI pipeline tests
  • 📈 feat: implement analytics tracking for user engagement
  • 🔒️ fix: strengthen authentication password requirements
  • ♿️ feat: improve form accessibility for screen readers

Example of splitting commits:

  • First commit: ✨ feat: add new solc version type definitions
  • Second commit: 📝 docs: update documentation for new solc versions
  • Third commit: 🔧 chore: update package.json dependencies
  • Fourth commit: 🏷️ feat: add type definitions for new API endpoints
  • Fifth commit: 🧵 feat: improve concurrency handling in worker threads
  • Sixth commit: 🚨 fix: resolve linting issues in new code
  • Seventh commit: ✅ test: add unit tests for new solc version features
  • Eighth commit: 🔒️ fix: update dependencies with security vulnerabilities

Command Options

  • --no-verify: Skip running the pre-commit checks (lint, build, generate:docs)

Branch Naming Convention

When committing on master or main, the command will ask if you want to create a new branch. If yes, it creates a branch following this pattern:

<type>/<git-username>/<description>

Components:

  • <type>: The commit type (feature, fix, docs, refactor, perf, test, chore, etc.)
  • <git-username>: Your git username (obtained from git config user.name or the system username)
  • <description>: A kebab-case description of the change (e.g., add-user-auth, fix-login-bug)

Examples:

  • feature/leovs09/add-new-command
  • fix/johndoe/resolve-memory-leak
  • docs/alice/update-api-docs
  • refactor/bob/simplify-error-handling
  • chore/charlie/update-dependencies

Workflow:

  1. Command detects you're on master or main
  2. Asks: "You're on the main branch. Do you want to create a separate branch?"
  3. If "No": Proceeds with commit on current branch
  4. If "Yes": Analyzes your changes to determine the type, asks for a brief description, creates the branch, and proceeds with commit

Important Notes

  • By default, pre-commit checks (pnpm lint, pnpm build, pnpm generate:docs) will run to ensure code quality
  • If these checks fail, you'll be asked if you want to proceed with the commit anyway or fix the issues first
  • If specific files are already staged, the command will only commit those files
  • If no files are staged, it will automatically stage all modified and new files
  • The commit message will be constructed based on the changes detected
  • Before committing, the command will review the diff to identify if multiple commits would be more appropriate
  • If suggesting multiple commits, it will help you stage and commit the changes separately
  • Always reviews the commit diff to ensure the message matches the changes

© NeoLabHQ, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. 2 hidden characters (zero-width or bidirectional) removed. Raw file

Files

Just SKILL.md in skills/commit of NeoLabHQ/context-engineering-kit.

Open the folder on GitHubat commit 23e2428

Compare with similar skills

Commit 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.

Commit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit this skillNeoLabHQ/context-engineering-kit1.7k—~2.2kAutomated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • ToolJet Multi-Repo Commit

    ToolJet/ToolJet

    Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • 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.

    57k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • 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.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Saleor Commit Workflow

    saleor/saleor

    Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from NeoLabHQ/context-engineering-kit

All 57 skills in this repo

  • Prompt Engineering

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing…

    1.7k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • Git Notes

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides…

    1.7k GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Multi Agent Patterns

    NeoLabHQ/context-engineering-kit

    Design multi-agent architectures for complex tasks. An agent skill from NeoLabHQ/context-engineering-kit.

    1.7k GitHub starsUsed in 7 repos~6k tokens
    Auto-check passed

  • Load PR Comments

    NeoLabHQ/context-engineering-kit

    A skill your agent uses to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/.md for parallel agents to fix.

    1.7k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Review PR

    NeoLabHQ/context-engineering-kit

    Review an existing GitHub pull request and post inline review comments on its diff.

    1.7k GitHub stars~3.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Subagent Driven Development

    NeoLabHQ/context-engineering-kit

    A skill your agent uses when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or…

    1.7k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Commit

What does Commit do?

Create well-formatted commits with conventional commit messages and emoji. Commit is an agent skill from NeoLabHQ/context-engineering-kit.

When should I use Commit?

Commit fits situations like: tasks that involve Commit messages.

How do I install Commit in Claude Code?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill commit -a claude-code`. Or copy the skill folder (skills/commit in NeoLabHQ/context-engineering-kit) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install Commit in Codex?

Run `npx skills add NeoLabHQ/context-engineering-kit --skill commit -a codex`. Or copy the skill folder (skills/commit in NeoLabHQ/context-engineering-kit) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use Commit 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 NeoLabHQ/context-engineering-kit --skill commit -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, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.

What does Commit need to run?

Going by SKILL.md and its folder, Commit needs the command-line tools its instructions call (pnpm and git).

Does Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit 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 Commit use?

Commit is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit use?

About 2.2k tokens (SKILL.md is roughly 8.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?

Skills that share tags, products or a category with Commit: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit?

NeoLabHQ (a GitHub organization) maintains it in NeoLabHQ/context-engineering-kit, which has 1,748 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on August 26, 2026.

Source: NeoLabHQ/context-engineering-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.