Git Commit Convention

Enforce the Bedriftsgrafen project's git commit message format and pre-commit checks.

Updated Jan 10, 2026

Search Tags:#git #workflow #commit #pre-commit #policy #lint #convention

Ready to run

npx skills add https://github.com/Bedriftsgrafen/bedriftsgrafen.no --skill git-commit-convention

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Commit Convention
Source: https://github.com/Bedriftsgrafen/bedriftsgrafen.no/tree/main/.agent/skills/git_commit_convention
Command: npx skills add https://github.com/Bedriftsgrafen/bedriftsgrafen.no --skill git-commit-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces the Bedriftsgrafen project's strict git commit message format and policies.

Core Features & Use Cases

Enforces the standard commit format: <type>(<scope>): <subject>.
Guides pre-commit checks including tests, linting, and type checks to ensure message quality.

Quick Start

Follow the <type>(<scope>): <subject> format for every commit in the project.

Frequently Asked Questions about Git Commit Convention

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

FAQPage Schema

How do I enforce a strict git commit message format for my project?▼

To enforce a strict git commit message format, this Skill validates every commit against the <type>(<scope>): <subject> convention, ensuring consistent types, scopes, and subjects across all project commits.

What pre-commit checks should I run for linting and type validation?▼

Pre-commit checks should include running tests, linting, and type checks to validate code quality. This Skill provides a pre-commit checklist that ensures both code validation and commit message quality are completed before committing changes.

How does a commit convention policy work with git workflows?▼

A commit convention policy works by intercepting the git workflow to validate commit message structure before finalizing the commit. This Skill applies strict formatting rules to all commits across the project, guiding types, scopes, subjects, and optional body or footer text.

Do I need any external dependencies to apply a git commit convention?▼

No external dependencies are required to apply this git commit convention. The Skill operates independently to enforce the Bedriftsgrafen project's strict commit message format and pre-commit policies without relying on additional components.

When should I use the <type>(<scope>): <subject> commit format?▼

You should use the <type>(<scope>): <subject> commit format for every commit in a project that requires strict consistency. This Skill enforces this specific format, along with optional body and footer sections, to maintain a standardized git history across the entire project.

What is the best way to automate git commit linting before committing?▼

The best way to automate git commit linting is to integrate a pre-commit policy that checks message format and runs code validation. This Skill enforces commit conventions and guides pre-commit checks including tests, linting, and type checks to ensure quality before committing.