commit

Generate conventional git commit messages with validated types and issue references.

Updated May 5, 2026
One-click install
npx skills add https://github.com/yanochka11/harness_bro --skill commit-yanochka11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/ported/commit
Command: npx skills add https://github.com/yanochka11/harness_bro --skill commit-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create properly formatted git commits by applying consistent conventions, branch checks, and issue reference rules instead of manually crafting commit messages.

Core Features & Use Cases

  • Conventional Commit Formatting: Generates commit messages with validated types, scopes, subjects, bodies, and footers.
  • Commit Safety Guidance: Ensures work is not committed directly on protected main or master branches without creating a feature branch first.
  • AI Commit Attribution Rules: Applies appropriate attribution practices for changes created with coding agents while avoiding misleading metadata.
  • Use Case: A developer finishing a feature can use this Skill to prepare a review-ready commit message that follows repository standards and links related issues.

Quick Start

Use the commit skill to create a properly formatted git commit message for my current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How does branch validation work when committing to a protected branch?

Conventional commit formatting applies validated types, scopes, subjects, bodies, and footers to maintain version control history. It enforces repository standards for commit messages during software development workflows.

How do I format git commit messages with issue references?

Formatting git commit messages with issue references requires applying repository commit conventions and issue reference rules. This generates validated commit messages with proper types, scopes, subjects, bodies, and footers for version control history.

Can I use automated commit formatting directly on the main branch?

Direct commits to protected main or master branches are blocked by commit safety guidance. You must create a feature branch first before staging changes and preparing commits to maintain safe version control history.

What is the best way to maintain consistent git commit conventions?

Maintaining consistent git commit conventions is best achieved by applying structured formatting rules to validate types, scopes, and subjects. This ensures repository standards are met during version control workflows.

Does AI commit attribution require special metadata in git history?

AI commit attribution applies appropriate practices for coding agent changes while avoiding misleading metadata in git history. This ensures version control records accurately reflect AI-assisted contributions during software development workflows.

How do I stage and prepare git commits following repository standards?

Staging and preparing git commits following repository standards involves applying structured formatting rules, branch validation, and issue reference requirements. This produces review-ready commit messages that maintain consistent version control history.