commit

Generate conventional Git commits with emojis, tags, and GitHub releases.

Updated Nov 18, 2025

Search Tags:#git #version control #commit #conventional commits #tagging #github releases

Ready to run

npx skills add https://github.com/bashfulrobot/nixerator --skill commit-bashfulrobot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/bashfulrobot/nixerator/tree/main/modules/apps/cli/claude-code/skills/commit
Command: npx skills add https://github.com/bashfulrobot/nixerator --skill commit-bashfulrobot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Grep, Read, git, gh, and includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating well-formatted, conventional Git commits, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

Conventional Commits: Enforces a standardized commit message format (<type>(<scope>): <emoji> <description>).
Emoji Integration: Automatically adds relevant emojis to commit messages based on type.
Automated Tagging & Releases: Optionally creates signed Git tags and GitHub releases.
Use Case: When fixing a bug in the authentication module, you can create a commit like fix(auth): 🐛 resolve login redirect loop, which is automatically signed, pushed, and tagged if specified.

Quick Start

Use the commit skill to create a feat commit for adding a new user profile page.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I create conventional commits with emojis automatically?▼

Conventional commits with emojis are generated by enforcing a standardized message structure of type, scope, emoji, and description. This process automatically adds relevant emojis based on the commit type to ensure project history consistency.

Can I automate Git tagging and GitHub releases when making a commit?▼

Yes, Git tagging and GitHub release creation can be automated during the commit process. The workflow optionally creates signed Git tags and generates GitHub releases directly after structuring the commit message.

What is the correct format for a conventional commit message with a scope?▼

The correct conventional commit format is `<type>(<scope>): <emoji> <description>`. This structure enforces clarity by separating the commit type, affected module scope, visual emoji indicator, and descriptive summary.

Does this conventional commit workflow support atomic and signed commits?▼

Yes, the conventional commit workflow supports both atomic commits and signed commits. This ensures cryptographically verified history integrity and allows staging individual, isolated changes for precise project tracking.

Do I need Bash and GitHub CLI installed to automate signed Git tags?▼

Yes, Bash and the GitHub CLI (`gh`) are required dependencies to automate signed Git tags and releases. The workflow relies on these tools alongside `git` and `grep` to parse, structure, and push commit data.