Agent skill

Git Commit Format

by openshift-eng in openshift-eng/ai-helpers

Apply conventional commit formatting rules. An agent skill from openshift-eng/ai-helpers.

Apache-2.0Auto-check passedDevelopment

Install Git Commit Format

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill git-commit-format -a claude-code

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

GitHub CLI
$ gh skill install openshift-eng/ai-helpers git-commit-format --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/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/git/skills/git-commit-format .claude/skills/git-commit-format && 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
git-commit-format
GitHub stars
120
Token cost
~915 tokens
SKILL.md length
279 words
Files
1
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

Apply conventional commit formatting rules. An agent skill from openshift-eng/ai-helpers.

  • Works in 3 steps: Environment variables: $GIT_AUTHOR_NAME… → Git config: git config user.name and git… → If neither configured, ask user to…
  • Generating commit messages
  • SKILL.md covers Name, Synopsis, Description and Implementation, plus 5 more sections
  • Calls git and make

What it does

Git Commit Format is an agent skill from openshift-eng/ai-helpers. Apply conventional commit formatting rules. Use when generating commit messages or creating commits.

Its SKILL.md is about 920 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: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

When your agent uses it

  • Generating commit messages
  • Creating commits

Example prompts

  • “/git-commit-format”

Workflow steps

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

  1. Environment variables: $GIT_AUTHOR_NAME and $GIT_AUTHOR_EMAIL
  2. Git config: git config user.name and git config user.email
  3. If neither configured, ask user to provide details

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. 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
    • make

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

  • Network

    Links to these hosts (documentation or services it may open):

    • conventionalcommits.org

    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

Git Commit Format loads about 915 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 279 words of instructions outside code blocks.

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

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 openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 279 words, ~915 tokens.

Download SKILL.mdSave it as .claude/skills/git-commit-format/SKILL.md (or your agent's skills folder).
name
git-commit-format
description
Apply conventional commit formatting rules. Use when generating commit messages or creating commits.

Name

openshift-developer:git-commit-format

Synopsis

/openshift-developer:git-commit-format

Description

Applies conventional commit formatting rules when generating commit messages. This skill is loaded as context for other skills and workflows — it defines the commit message format, required footers, and validation rules.

Implementation

Commit Message Format
<type>(<scope>): <description>

[optional body]

[footers]
Commit Types
  • feat: New features
  • fix: Bug fixes
  • docs: Documentation changes
  • style: Code style changes (formatting, etc.)
  • refactor: Code refactoring (no functional changes)
  • test: Adding/updating tests
  • chore: Maintenance tasks
  • build: Build system or dependency changes
  • ci: CI/CD changes
  • perf: Performance improvements
  • revert: Revert previous commit
Breaking Changes

With ! to draw attention:

feat!: send email when product shipped

With BREAKING CHANGE footer:

feat: allow config to extend other configs

BREAKING CHANGE: `extends` key now used for extending config files
Required Footers
Signed-off-by

ALWAYS include Signed-off-by footer with name and email.

Get credentials in this priority order:

  1. Environment variables: $GIT_AUTHOR_NAME and $GIT_AUTHOR_EMAIL
  2. Git config: git config user.name and git config user.email
  3. If neither configured, ask user to provide details
Commit-Message-Assisted-by

ALWAYS include when Claude assists with creating or generating the commit message:

Commit-Message-Assisted-by: Claude (via Claude Code)
Gitlint Validation Rules
  • Run make run-gitlint to validate commit messages (if the repo has a gitlint target)
  • Title line: 120 characters maximum
  • Body line: 140 characters maximum per line
  • Use conventional commit format
  • Include required footers (Signed-off-by)
  • No trailing whitespace

Return Value

  • Commit message: A conventional commit message with type, scope, description, body, and all required footers
Show full SKILL.md (148 more words)Show less

Examples

  1. Simple commit:

    docs: correct spelling of CHANGELOG
    
    Signed-off-by: Jane Doe <jdoe@example.com>
    Commit-Message-Assisted-by: Claude (via Claude Code)
  2. With scope:

    feat(azure): add workload identity support
    
    Signed-off-by: Jane Doe <jdoe@example.com>
    Commit-Message-Assisted-by: Claude (via Claude Code)
  3. Multi-paragraph with footers:

    fix: prevent racing of requests
    
    Introduce request ID and reference to latest request. Dismiss
    incoming responses other than from latest request.
    
    Remove timeouts which were used to mitigate racing but are
    obsolete now.
    
    Reviewed-by: John Smith
    Refs: #123
    Signed-off-by: Jane Doe <jdoe@example.com>
    Commit-Message-Assisted-by: Claude (via Claude Code)

Arguments

  • None. This skill provides formatting rules as context for other skills and workflows.

Quick Checklist

When creating commits:

  • Use conventional commit format: <type>(<scope>): <description>
  • Title under 120 characters
  • Body lines under 140 characters
  • Include Signed-off-by footer
  • Include Commit-Message-Assisted-by: Claude (via Claude Code) footer
  • Validate with make run-gitlint if available
  • Use "!" or BREAKING CHANGE for breaking changes

Reference

Conventional Commits Specification: https://www.conventionalcommits.org/en/v1.0.0/#specification

© openshift-eng, 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/git/skills/git-commit-format of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176

Compare with similar skills

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

Git Commit Format compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Commit Format this skillopenshift-eng/ai-helpers120—~915Automated safety check: PassApache-2.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-skills102k2 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 today
    DevelopmentAuto-check passed
  • 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 today
    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.

    102k 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 today
    DevelopmentAuto-check passed
  • 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 today
    DevelopmentAuto-check passed
  • 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 openshift-eng/ai-helpers

All 118 skills in this repo
  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Git Commit Format

What does Git Commit Format do?

Apply conventional commit formatting rules. An agent skill from openshift-eng/ai-helpers. Git Commit Format is an agent skill from openshift-eng/ai-helpers. Apply conventional commit formatting rules.

When should I use Git Commit Format?

Git Commit Format fits situations like: generating commit messages; creating commits.

How do I install Git Commit Format in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill git-commit-format -a claude-code`. Or copy the skill folder (plugins/git/skills/git-commit-format in openshift-eng/ai-helpers) into .claude/skills/git-commit-format in your project. Claude Code loads it when a task matches its description.

How do I install Git Commit Format in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill git-commit-format -a codex`. Or copy the skill folder (plugins/git/skills/git-commit-format in openshift-eng/ai-helpers) into .agents/skills/git-commit-format in your project. Codex loads it when a task matches its description.

Can I use Git Commit Format 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 openshift-eng/ai-helpers --skill git-commit-format -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-commit-format, .gemini/skills/git-commit-format, .github/skills/git-commit-format and .opencode/skills/git-commit-format in your project.

What does Git Commit Format need to run?

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

Does Git Commit Format access the network?

SKILL.md names 1 domain. As links in the text: conventionalcommits.org. This is read from the text; nothing was executed.

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

Git Commit Format 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 Git Commit Format use?

About 915 tokens (SKILL.md is roughly 3.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 Git Commit Format?

Skills that share tags, products or a category with Git Commit Format: 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, 102k 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 Git Commit Format?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.