git-lib-commit

Generate Conventional Commits messages from code diffs with intelligent file staging.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/bryandrenner/ai-agent-configs --skill git-lib-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-lib-commit
Source: https://github.com/bryandrenner/ai-agent-configs/tree/main/opinionated/copilot/skills/git-commit
Command: npx skills add https://github.com/bryandrenner/ai-agent-configs --skill git-lib-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes git commit messages using the Conventional Commits specification, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

  • Conventional Commits: Adheres to a widely adopted standard for commit messages.
  • Intelligent Staging: Helps in staging files logically before committing.
  • Message Generation: Assists in creating descriptive commit messages based on changes.
  • Use Case: When you've finished a bug fix, use this skill to create a commit message like fix: resolve user login issue with appropriate scope and description.

Quick Start

Use the git-commit skill to create a conventional commit for your staged changes.

Frequently Asked Questions about git-lib-commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from my git diff?

You can generate conventional commit messages automatically by analyzing your code diffs. This skill automates the creation of commit messages adhering to the Conventional Commits specification, producing descriptive outputs based on your staged changes.

What is the best way to stage files logically before making a conventional commit?

The best way to stage files logically before a conventional commit is using intelligent staging. This skill facilitates logical file staging and generates descriptive commit messages from the resulting code diffs.

Does this conventional commit generator support commit types like feat, fix, and refactor?

Yes, this conventional commit generator supports various commit types including feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. It also provides options for defining scopes and indicating breaking changes.

How do I indicate breaking changes in my automated conventional commit messages?

You can indicate breaking changes in automated conventional commit messages by utilizing the skill's built-in breaking change options. It standardizes your git commit messages while supporting specific types, scopes, and breaking change flags.

Can I use this skill to standardize git commit messages for an existing project?

Yes, you can use this skill to standardize git commit messages for an existing project. It ensures consistency and clarity in your project's history by adhering to the widely adopted Conventional Commits specification.