Read and follow the canonical commit-format policy in ../../../skills/git-commit-format/SKILL.md whenever generating commit messages or discussing commit practices.
Apply HyperShift conventional commit formatting rules. Use when generating commit messages or creating commits.
Ask your Agent
Use this Skill: https://skilld.dev/gh/openshift/hypershift/git-commit-format
This session only. Nothing lands on disk.
SKILL.md
327 B≈33 tokens always: the name and description. ≈42 when used: this file.
Source: SKILL.md on GitHub
Third-party checks
1 warning6mo4 checks · Risk SAFE
- Gen Agent Trust Hub7mo
This skill defines Git commit formatting rules and validation steps. It is generally safe but presents a minor risk of indirect prompt injection as it processes repository content and executes a local 'make' command for validation.
- Socket6mo
No alerts
- Snyk7mo
Risk: LOW · No issues
- Runlayer7mo
1/1 file flagged
Provenance
Signed by skilld at a1283f8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.
Activeupdated last week
Topics
- Git/VCS
- commits
- conventional-commits
- hypershift
- openshift
- gitlint
- formatting
README badge
What it does
Enforces HyperShift's conventional commit format with required Signed-off-by and Commit-Message-Assisted-by footers, validated via gitlint. Use when generating or creating commits in the HyperShift project to ensure title lines stay under 120 characters and body lines under 140 characters.
Generated from the current SKILL.md.
Frequently asked
What footers are required in every commit message?
Two footers are always required: `Signed-off-by` with your name and email (from git config or environment variables), and `Commit-Message-Assisted-by: Claude (via Claude Code)` when Claude generates the message.
What are the character limits for commit messages?
The title line has a maximum of 120 characters, and body lines must not exceed 140 characters per line.
How do I indicate a breaking change?
Use either a `!` after the type (e.g., `feat!:`) or include a `BREAKING CHANGE` footer in the message, or both for clarity.
How do I validate commit messages?
Run `make run-gitlint` to validate that your commit messages meet the HyperShift conventional commit rules and character limits.
What commit types are allowed?
The allowed types are: feat, fix, docs, style, refactor, test, chore, build, ci, perf, and revert. Each type should be followed by an optional scope in parentheses and a description.
Generated from the current SKILL.md. These answers refresh after source changes.