git-commit-instructions

Generate conventional git commit messages with bullet lists from repository state.

1|Updated Mar 14, 2026

Search Tags:#git #commit #safety #conventional-commits #message-generation #branch-tickets

Ready to run

npx skills add https://github.com/RussBrown00/agent-skills --skill git-commit-instructions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-instructions
Source: https://github.com/RussBrown00/agent-skills/tree/main/git-commit-instructions
Command: npx skills add https://github.com/RussBrown00/agent-skills --skill git-commit-instructions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual, error-prone commit message drafting with a standardized, ticket-aware workflow that enforces conventional commit structure and a clear changelog.

Core Features & Use Cases

Generates conventional commit headers from the current git state, including an automatic 2-line format and a bullet list of changes.
Detects ticket IDs from branch names (e.g., SC-###) and prefixes headers accordingly to improve traceability.
Enforces safety practices by warning about sensitive files, guiding proper staging, and avoiding destructive actions without explicit consent.

Quick Start

Invoke the git-commit-instructions skill to generate and apply a conventional commit from the current git state.

Frequently Asked Questions about git-commit-instructions

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

FAQPage Schema

How do I generate conventional commit messages automatically from my current git state?▼

Generating conventional commit messages automatically requires analyzing your current git state and staged changes. This process creates a review-friendly, 2-line structured header and a detailed bullet list of modifications to replace manual drafting.

How do I automatically extract ticket IDs from my branch name for git commits?▼

Extracting ticket IDs from branch names for git commits involves parsing patterns like SC-### from the branch. The system automatically prefixes your conventional commit header with this detected ticket ID to improve traceability.

Can I automatically stage changes when creating conventional commits?▼

Yes, you can automatically stage changes when creating conventional commits upon explicit request. The workflow guides proper staging operations while enforcing safety checks to prevent accidental destructive actions.

What safety checks are applied during git commit operations?▼

Safety checks during git commit operations include warning about sensitive files and avoiding destructive actions without explicit consent. These precautions ensure proper staging and secure commit generation.

How do I handle work in progress changes when generating a standardized git commit?▼

Handling work in progress changes when generating a standardized git commit involves specific WIP formatting rules. The system applies these rules to ensure temporary states are clearly marked and safely committed.