skills.rest
baselakkad585-maker
baselakkad585-makerCOMMUNITY
Explore all skills by this author →
GitHub

commit

Enforce conventional commit message formats and issue references.

Updated Mar 28, 2026
Search Tags:#automation#git#commit#branching#code-quality#commit-message#conventional-commits
One-click install
npx skills add https://github.com/baselakkad585-maker/basel-dev-skills --skill commit-baselakkad585-maker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/baselakkad585-maker/basel-dev-skills/tree/main/skills/commit
Command: npx skills add https://github.com/baselakkad585-maker/basel-dev-skills --skill commit-baselakkad585-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures all code changes follow established commit conventions, preventing ad hoc or inconsistent messages that hinder changelogs and traceability.

Core Features & Use Cases

  • Conventional commit formatting: enforces the header type, scope, and subject in the correct format.
  • Issue references and footers: automatically includes references to related GH issues or SENTRY tickets when provided.
  • Branch guardrails: prompts branch creation when on main/master and verifies the current branch before committing.
  • Workflow integration: pairs with create-branch to streamline the branching step during the commit flow.
  • Audit-friendly history: ensures messages are within length constraints and maintain consistency across the repository.

Quick Start

Before making a commit, invoke this skill to format and validate your message according to conventional commits.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce conventional commit messages automatically across feature and hotfix branches?▼

Conventional commit messages are enforced automatically by validating the header format, subject length, and footer references for every code change across feature, hotfix, and release workflows.

What is the correct format for conventional commit headers and issue references?▼

Conventional commit headers must follow the type(scope): subject format, ensuring the subject stays within length constraints and the footer automatically includes references to related GitHub issues or Sentry tickets.

How do I prevent accidental commits to main or master branches?▼

Branch guardrails prevent accidental commits to main or master by prompting branch creation and verifying the current branch before allowing a commit to proceed.

Can I integrate branch creation directly into my commit workflow?▼

Branch creation integrates directly into the commit workflow by pairing with create-branch to streamline the branching step when the current branch is main or master.

Why do inconsistent commit messages hinder changelogs and traceability?▼

Inconsistent commit messages hinder changelogs and traceability because ad hoc formatting breaks automated history parsing; enforcing conventional commits ensures audit-friendly repository consistency.

Do I need to provide issue tickets for every conventional commit?▼

Issue tickets are not strictly required for every conventional commit, but footer references are automatically included when GitHub issues or Sentry tickets are provided during the commit flow.

Related Skills

Explore More Software Engineering Skills→
fredrikaverpilfredrikaverpil
253

git-commit

Validate git commit messages against the Conventional Commits specification.

Community
Basic
markjoshwelmarkjoshwel

git-majo

Execute a standardized git workflow with conventional commit messages.

Community
Advanced
metalagmanmetalagman
21

gitflow

Enforce Gitflow branching conventions and PR targets across develop and master branches.

Community
Advanced
sunLeeesunLeee

convention-commit

Enforce Conventional Commits format for Git commit messages.

Community
Intermediate