blade-commit

Name: blade-commit
Availability: InStock
Author: tiantien

Generate Gitmoji-formatted commit messages for staged changes.

Updated Apr 22, 2026

Search Tags:#git #workflow #repository #gitmoji #version-control #commit-message

Ready to run

npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-commit-tiantien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blade-commit
Source: https://github.com/tiantien/team-ai-coding-plugin/tree/main/skills/blade-commit
Command: npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-commit-tiantien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns raw code changes into clean, policy-compliant Git commits, so teams can record work consistently without hand-writing commit messages.

Core Features & Use Cases

Gitmoji-first commits: Produces one-line messages by default and detailed multi-line commits only when explicitly requested.
Commit safety guardrails: Prevents push, pull, rebase, merge, and other non-commit operations while keeping messages free of AI signatures.
Style adaptation: Matches the repository's existing commit language and tone, whether the project history is Chinese, English, or mixed.
Use case: Use it when you have staged changes from a feature, bug fix, refactor, or documentation update and want a uniform commit message.

Quick Start

Ask the skill to generate and run a Git commit for your staged changes using the project's preferred Gitmoji style without performing any remote operations.

Frequently Asked Questions about blade-commit

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

FAQPage Schema

How do I generate consistent git commit messages automatically?▼

Yes, you can use Gitmoji for multi-file commits. The skill processes staged changes across source code, documentation, and configuration files, generating a single safe, consistent commit message that applies the mandatory Gitmoji formatting to describe all included modifications.

Does this git commit workflow support both Chinese and English repository histories?▼

The skill enforces strict commit-only behavior, rejecting remote or destructive git operations to ensure safe commits. It prevents push, pull, rebase, and merge actions while keeping generated commit messages free of AI signatures.

How do I get a detailed changelog instead of a one-line git commit message?▼

Before generating a commit message, you must stage source code changes, documentation updates, or configuration edits in your git repository. The skill requires pre-staged files to analyze and does not perform staging or destructive operations itself.

Best way to format git commits for staged changes without writing them manually?▼

After generating consistent git commits, downstream actions include pushing to remote repositories, triggering CI/CD pipelines, or publishing version release notes. These actions extend version control workflows by distributing the safely committed changes.

What are the limitations of automated gitmoji commit generation?▼

Complementary tools include git staging assistants, branch managers, and code reviewers within the version-control workflow. These tools work in synergy to prepare changes, manage branches, and validate code before the commit message generation occurs.