git-workflow

Generate Conventional Commits, manage branches, and create Pull Request descriptions.

84|15|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/AIDotNet/MoYuCode --skill git-workflow-aidotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/AIDotNet/MoYuCode/tree/main/skills/community/git-workflow
Command: npx skills add https://github.com/AIDotNet/MoYuCode --skill git-workflow-aidotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates repetitive Git operations, ensuring consistent commit messages, streamlined branch management, and clear Pull Request descriptions, saving developers time and improving code quality.

Core Features & Use Cases

  • Conventional Commits: Automatically generates commit messages following the Conventional Commits specification (feat, fix, docs, etc.).
  • Branch Naming: Suggests and enforces standardized branch naming conventions (e.g., feature/, fix/).
  • PR Description Generation: Creates detailed PR descriptions based on commit history and user input.
  • Use Case: When you finish a new feature, you can use the /commit command to generate a feat: commit message, then use /branch to create a feature/your-feature-name branch, and finally use /pr to generate a PR description summarizing your changes.

Quick Start

Use the git-workflow skill to generate a conventional commit message for a new feature.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I automatically generate conventional commit messages for my Git changes?

To generate conventional commit messages automatically, this Skill analyzes your Git changes and produces messages following the Conventional Commits specification (feat, fix, docs, etc.). You can use the /commit command to ensure consistent version control practices and save development time.

What is the best way to create a standardized Git branch name for a new feature?

The best way to create a standardized Git branch name is using this Skill to enforce naming conventions like feature/ or fix/ prefixes. It suggests and applies structured branch naming to streamline your branch management and maintain consistency across your version control workflow.

How do I generate a Pull Request description from my commit history?

Generating a Pull Request description from commit history is done by using the /pr command to summarize your changes. This Skill analyzes your commit messages and user input to create detailed PR descriptions, ensuring clear communication of your software development modifications.

Can I automate my entire Git workflow from branching to Pull Request creation?

Yes, you can automate your entire Git workflow by combining the /commit, /branch, and /pr commands. This Skill sequentially generates conventional commit messages, creates standardized branches, and produces detailed Pull Request descriptions to streamline your version control automation.

Do I need to understand Git commands to use this workflow automation?

Yes, understanding Git commands and commit message structures is required to use this workflow automation effectively. The Skill automates repetitive Git operations but relies on your foundational knowledge of version control practices and Conventional Commits specifications.

When should I not use automated commit message generation?

Automated commit message generation should be avoided for highly complex or sensitive commits requiring nuanced manual context. This Skill applies standardized Conventional Commits formatting, which may not capture intricate architectural decisions that need custom developer explanations in version control.