skills.rest
iani-kuli
iani-kuliCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Enforce conventional commit formats and branch safety for git commits.

Updated May 5, 2026
Search Tags:#automation#git#workflow#version control#commit#sentry
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill commit-iani-kuli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/commit
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill commit-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates inconsistent, poorly formatted, or uninformative git commit messages that hinder project history and automated changelog generation.

Core Features & Use Cases

  • Conventional Commits: Enforces the standard type(scope): subject format with proper issue references.
  • Branch Safety: Automatically prevents commits to protected branches like main or master without a feature branch.
  • Use Case: When finishing a bug fix, use this skill to generate a compliant commit message that references the internal ticket and follows the required imperative mood.

Quick Start

Ask the assistant to commit your current changes using the Sentry commit convention and include the relevant issue reference.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I format git commit messages to follow Sentry conventions?▼

This skill standardizes git commits by enforcing the conventional commit format type(scope): subject. It ensures your messages use imperative mood, meet character limits, and include proper issue references for Sentry workflows.

How can I prevent accidental commits to protected branches like main?▼

Preventing accidental commits to protected branches like main requires automated branch safety protocols. This skill automatically blocks direct commits to main or master, ensuring changes are only made through a feature branch.

How do I add issue references to conventional commit messages?▼

Adding issue references to conventional commits involves appending the ticket number to the type(scope): subject format. This skill standardizes this process, linking your structured version control history directly to automated issue tracking.

Does this git workflow automation support AI-generated code attribution?▼

Yes, this git workflow automation supports AI-generated code attribution. It enforces structured version control protocols that require proper attribution for AI-generated code within your conventional commit messages.

What is the best way to automate changelog generation from git history?▼

Automating changelog generation from git history requires consistent, structured commit messages. This skill eliminates poorly formatted messages by enforcing standard conventional commit formats with proper type, scope, and subject definitions.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced
BaGyun0107BaGyun0107

commit

Generate Conventional Commits messages from code diffs.

Community
Basic
sebnowsebnow
8

source-control-hygiene

Enforce atomic commits with conventional messages across git and jujutsu workflows.

Community
Advanced
mkittmkitt
6

git-standards

Enforce Git commit message and branch naming conventions.

Community
Basic