Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Format

Official
openshift·vlatest·backend·Apache-2.0

Helps with Git, formatting as part of developing backend services and APIs workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it Git Commit Format, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add openshift/hypershift --skill "Git Commit Format" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

openshift

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned openshift/hypershift at dd2a3e4e4a.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
dd2a3e4e4a
Manifest
.claude/skills/git-commit-format/SKILL.md
Scanned
1 file, 7 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The Git Commit Format skill enforces strict adherence to conventional commit standards within Hypershift workflows. It automatically structures commit messages to include type, scope, and description, ensuring consistency across your codebase history.

When to use it

  • Standardizing commit logs for large teams using OpenShift or Hypershift environments.
  • Automating changelog generation by parsing structured commit types (e.g., feat, fix).
  • Preparing repositories for release management tools that rely on semantic versioning.
  • Enforcing code quality gates in CI/CD pipelines before merging to main branches.

Key capabilities

  • Validates message structure against conventional commit guidelines.
  • Integrates directly with Hypershift deployment workflows.
  • Formats messages to include specific metadata like scope and breaking changes.
  • Prevents non-compliant commits from proceeding in automated pipelines.

Example prompts

  • "Format this commit message to follow the Git Commit Format standard for a feature addition."
  • "Validate the current branch's commit history against the Hypershift conventional commit rules."
  • "Generate a commit message for a bug fix in the networking module using the required format."

Tips & gotchas

Ensure your team agrees on specific prefixes (like feat, fix) before enabling this skill, as it enforces strict patterns. This skill is designed specifically for Hypershift contexts; applying it to unrelated Git repositories may cause unnecessary validation errors.