git-commit

Automate Git commit, push, and pull request workflows with structured messages.

1|1|Updated Jan 18, 2025
One-click install
npx skills add https://github.com/Project-X-Vietnam/landing-page --skill git-commit-project-x-vietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Project-X-Vietnam/landing-page/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/Project-X-Vietnam/landing-page --skill git-commit-project-x-vietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and standardizes the Git commit, push, and pull request process, ensuring consistent and descriptive commit messages and efficient branch management.

Core Features & Use Cases

  • Structured Commits: Enforces a clear commit message format (<type>: <description>) for better code history.
  • Branch Naming Conventions: Provides standard prefixes for feature, fix, style, and refactor branches.
  • Automated PR Creation: Generates pull requests with a predefined template for summary and test plans.
  • Use Case: When you've finished a new feature, use this Skill to stage your changes, write a descriptive commit message like feat: implement user profile page, push your branch, and create a pull request with gh pr create.

Quick Start

Use the git-commit skill to stage all changes, commit them with the message "feat: add new login component", and push to the remote repository.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate git commit messages and pull request workflows?

To automate git commit messages and pull request workflows, you can use command-line Git operations and GitHub CLI integration to enforce structured message formats like `<type>: <description>` and generate predefined PR templates.

What is the standard format for structuring Git commit messages?

The standard format for structuring Git commit messages is `<type>: <description>`. This structured format ensures consistent and descriptive code history across feature development, bug fixing, refactoring, and documentation updates.

How do I create a pull request with a predefined template using GitHub CLI?

You can create a pull request with a predefined template using GitHub CLI by executing `gh pr create` after pushing your branch, which automatically generates a PR with structured summary and test plan sections.

What branch naming conventions should I use for feature development and bug fixing?

For feature development and bug fixing, you should use standard branch naming conventions with specific prefixes for features, fixes, styles, and refactors to ensure efficient and organized branch management.

Does this Git workflow automation require any external dependencies or tools?

This Git workflow automation requires no external dependencies, relying solely on standard command-line Git operations and GitHub CLI integration to manage staging, committing, pushing, and pull request creation.

Can I use this workflow for code refactoring and documentation updates?

Yes, you can use this workflow for code refactoring and documentation updates by applying the appropriate branch prefixes and structured commit types to maintain consistent version control management across different development tasks.