skills.rest
AsiaOstrich
AsiaOstrichCOMMUNITY
Explore all skills by this author →
𝕏@AsiaOstrichGitHub

commit

Generate Conventional Commits messages from staged Git changes.

70|13|Updated Dec 24, 2025
Search Tags:#git#version control#bug fix#commit#conventional commits#code history#refactor
One-click install
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill commit-asiaostrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/AsiaOstrich/universal-dev-standards/tree/main/.gemini/skills/commit-standards
Command: npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill commit-asiaostrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you generate clear, consistent, and standard-compliant commit messages, improving code history readability and automation.

Core Features & Use Cases

  • Conventional Commits: Automatically generates messages following the Conventional Commits standard.
  • Change Analysis: Analyzes staged Git changes to suggest appropriate commit types and scopes.
  • Use Case: Before committing a bug fix, you can use this Skill to generate a fix(...) commit message that clearly describes the problem and solution, linking it to the relevant issue.

Quick Start

Use the commit skill to generate a commit message for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged Git changes?▼

To generate conventional commit messages, this Skill analyzes your staged Git changes and automatically suggests appropriate commit types, scopes, and detailed bodies matching the Conventional Commits standard for a seamless workflow.

What is the Conventional Commits standard and how does it improve code history?▼

The Conventional Commits standard is a structured format for commit messages using types like feat, fix, or refactor. It improves code history readability and enables automation by clearly describing code changes and linking them to issues.

Can I include issue references and breaking changes in my Git commit messages?▼

Yes, you can include issue references and breaking changes in your Git commit messages. The Skill generates detailed footers to document breaking changes or link relevant issue references directly within the commit message structure.

Does this commit message generator automatically detect the correct commit type for a bug fix?▼

Yes, it automatically detects the correct commit type for a bug fix. By analyzing your staged Git changes, it suggests the appropriate type, such as a fix commit, and scopes to accurately describe the problem and solution.

What's the best way to format a Git commit message for a code refactor?▼

The best way to format a Git commit message for a code refactor is using the Conventional Commits standard. This Skill analyzes your staged changes and suggests a refactor commit type with appropriate scopes and descriptive bodies.

Related Skills

Explore More Software Engineering Skills→
JoNaYeonJoNaYeon
1

work_git_commit-message

Analyze staged git diffs and generate Conventional Commits messages.

Community
Intermediate
JasonLoJasonLo

ss-self-release

Automate version bumping, Git tagging, and pushing to remote repositories.

Community
Advanced
dallenpyrahdallenpyrah

setup-pre-commit

Automate Husky pre-commit hook setup with lint-staged and custom scripts.

Community
Intermediate
kevinrobaynakevinrobayna

commit

Generate conventional Git commit messages from analyzed code changes.

Community
Intermediate