gh-commit

Generate Conventional Commits messages from staged and unstaged Git changes.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/flora131/atomic --skill gh-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-commit
Source: https://github.com/flora131/atomic/tree/main/.opencode/skills/gh-commit
Command: npx skills add https://github.com/flora131/atomic --skill gh-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted Git commits, adhering to the Conventional Commits specification, which improves code review and automated changelog generation.

Core Features & Use Cases

  • Automated Commit Message Generation: Creates commit messages based on code changes, following the Conventional Commits standard.
  • Conventional Commits Enforcement: Guides users to write clear, structured commit messages for better project history.
  • Use Case: When you've made several related changes, this skill helps you craft a single, descriptive commit message that clearly communicates the purpose and impact of your changes.

Quick Start

Use the gh-commit skill to create a commit message for your staged changes.

Frequently Asked Questions about gh-commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from staged changes?

You can generate conventional commit messages automatically by analyzing staged and unstaged changes to produce descriptive messages including type, scope, and body, enforcing best practices for commit history management.

What is the best way to break down a large Git commit into conventional commits?

To break down a large Git commit, analyze your staged and unstaged changes to suggest splitting commits when necessary, generating structured messages that clearly communicate the purpose and impact of each change.

Can I use conventional commits to improve code review and automated changelog generation?

Conventional commits improve code review and automated changelog generation by enforcing a structured format with type, scope, and body, creating a cleaner Git history for automated tools to parse.

How do pre-commit hooks enforce conventional commits in Git?

Pre-commit hooks enforce conventional commits by integrating with the commit process to ensure messages follow the specification, analyzing changes and suggesting breakdowns to maintain a clean project history.

Does this conventional commit tool work without external dependencies?

Yes, this conventional commit tool works without external dependencies, analyzing staged and unstaged changes directly to generate well-formatted messages adhering to the specification.