fredrikaverpil

git-commit

@fredrikaverpil/git-commit
fredrikaverpil
190
6 forks
Updated 1/6/2026
View on GitHub

Use this skill BEFORE running any git commit command. Triggers when about to run `git commit`. Ensures commit messages follow Conventional Commits specification.

Installation

$skills install @fredrikaverpil/git-commit
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Repositoryfredrikaverpil/dotfiles
Pathstow/shared/.claude/skills/git-commit/SKILL.md
Branchmain
Scoped Name@fredrikaverpil/git-commit

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions

name: git-commit description: Use this skill BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification.

Git Commit Messages

Write commit messages following the Conventional Commits specification.

Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Types

TypePurpose
featNew feature
fixBug fix
docsDocumentation only
styleCode style (formatting, no logic change)
refactorCode change that neither fixes a bug nor adds a feature
perfPerformance improvement
testAdding or correcting tests
buildBuild system or external dependencies
ciCI configuration
choreMaintenance tasks
revertReverts a previous commit

Rules

  1. Use imperative mood in description ("add feature" not "added feature")
  2. Do not end description with a period
  3. Keep description under 72 characters
  4. Separate subject from body with a blank line
  5. Use body to explain what and why, not how

Breaking Changes

Add ! after type/scope or include BREAKING CHANGE: in footer:

feat(api)!: remove deprecated endpoints

BREAKING CHANGE: The /v1/users endpoint has been removed.

Scope

Optional. Use to specify area of change (e.g., api, ui, auth, db).

Attribution

Do NOT include any AI attribution, co-author tags, or generated-by footers in commit messages.

More by fredrikaverpil

View all
gh-pr
190

Use this skill when creating a GitHub pull request. Defines PR body format with Why/What/Notes sections and ensures proper assignment.

aip
190

Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.

golang-style
190

Use this skill BEFORE writing or editing any Go (.go) files. Triggers when about to create, modify, or add code to .go files. Enforces happy path coding, error wrapping, sentinel errors, and godoc-style comments.

jira-cli
190

Jira CLI command reference. Use when working with Jira issues, epics, sprints, or any Jira operations from the command line.