commit-message

Generate Angular-style commit messages from git status and diffs.

Updated Feb 25, 2024
One-click install
npx skills add https://github.com/GyroZepelix/.dotfiles --skill commit-message-gyrozepelix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/GyroZepelix/.dotfiles/tree/main/02-agentic-llms/.claude/skills/commit-message
Command: npx skills add https://github.com/GyroZepelix/.dotfiles --skill commit-message-gyrozepelix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes git changes and generates concise, Angular-style commit messages without scope, prompting for staging choices and requiring user approval before committing.

Core Features & Use Cases

  • Analyze git status and diffs to understand changes
  • Generate a type-prefixed lowercase subject line (no scope, no body) within 72 chars
  • Prompt for staging strategy and commit only after explicit approval
  • Enforce Angular commit conventions and provide a consistent workflow across repos
  • Use Case: when you modify files and want a clean, standard commit message, run /commit-message and approve the suggestion

Quick Start

Run /commit-message to analyze your changes and generate a one-line Angular-style commit message, then approve the suggestion to commit

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I generate Angular-style git commit messages automatically?

To generate Angular-style git commit messages automatically, this Skill inspects your git status and diffs to create a concise, type-prefixed lowercase subject line. It enforces a strict 72-character limit and requires your explicit approval before running git add and git commit.

What is the Angular commit convention for writing a git commit message?

The Angular commit convention enforced here requires selecting a type from a predefined list and writing a lowercase subject line with no scope and no body. This ensures a clean, standardized one-line history across repositories.

How do I decide which files to stage before committing my code changes?

To decide which files to stage before committing your code changes, this Skill prompts you for a staging strategy after analyzing your git status. It guides your staging decisions and only commits the selected changes after you explicitly approve the generated message.

Can I include a detailed body and scope in my Angular commit messages?

No, you cannot include a detailed body or scope in your Angular commit messages with this Skill. It strictly enforces a one-line format by generating a type-prefixed subject without scope or body, capped at 72 characters.

Does this Angular commit generator work with any git repository?

Yes, this Angular commit generator works with any git repository where you want to commit changes. It applies a consistent Angular commit workflow across your repos by analyzing local git diffs and status without requiring specific project structures.