git-commit

Draft Angular-style Git commit messages from staged changes.

14.2k|717|Updated Nov 15, 2022
One-click install
npx skills add https://github.com/tisfeng/Easydict --skill git-commit-tisfeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/tisfeng/Easydict/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/tisfeng/Easydict --skill git-commit-tisfeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft Angular-style Git commit messages from staged changes and execute git commit safely after explicit approval. Use for commit message generation, staged-diff review for commit wording, and Chinese previews of English commit messages.

Core Features & Use Cases

  • Generate commit messages in Angular format from diffs of staged changes.
  • Review and refine the message before committing.
  • Chinese previews of English commit messages for bilingual teams.

Quick Start

Stage your changes, ask for a draft Angular-style commit message, review it, then approve to run the commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate Angular-style Git commit messages from staged changes?

To generate Angular-style Git commit messages, you stage your changes and the tool gathers the git status and staged diff to draft a standardized commit message. It also shows the current branch and recent logs for context before requiring your explicit approval to commit.

Can I preview English Git commit messages in Chinese before committing?

Yes, you can preview English Git commit messages in Chinese before committing. The tool provides Chinese previews of the generated Angular-style English commit messages, which is designed to help bilingual teams review and refine commit wording safely.

What is the Angular commit message format and when should I use it?

The Angular commit message format is a standardized convention for structuring commit history using specific type prefixes and scopes. You should use it when you want to standardize your project's commit history and need a reviewed, safe commit message generated directly from your staged diffs.

How do I safely automate Git commits without accidentally committing the wrong changes?

To safely automate Git commits, this tool reviews the staged diff and drafts a commit message, but it requires explicit approval before executing the commit. This ensures you can review the generated Angular-style message and the staged changes before anything is committed.

Does the commit message generation workflow work without any external dependencies?

Yes, the commit message generation workflow works without external dependencies. It operates by gathering your local git status, diffing the staged changes, and showing recent logs to draft the Angular-style commit message directly within your environment.

Why does my automated commit message not match the staged diff accurately?

If your automated commit message does not match the staged diff, ensure you have properly staged your changes before generation. The tool drafts the Angular-style commit message based on the staged diff, so unstaged changes will not be reflected in the wording.