git-helper

Analyze git changes and propose commit messages and next actions.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/miles990/skillpkg --skill git-helper-miles990
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-helper
Source: https://github.com/miles990/skillpkg/tree/main/skills/git-helper
Command: npx skills add https://github.com/miles990/skillpkg --skill git-helper-miles990

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams enforce consistent Git practices by generating standardized commit messages, recommending branch naming conventions, and guiding pull request workflows to maintain a clean project history.

Core Features & Use Cases

  • Commit Message Guidance: Generate conventional commit-style messages tailored to the changes.
  • Branch & PR Workflow: Suggest branch naming and PR preparation steps to speed up code reviews.
  • Use Case: When preparing a feature branch, run this Skill to get a ready-to-use commit message, a suggested branch name, and a PR checklist.

Quick Start

To begin, describe the changes you made and the desired outcome. Example:

  • Action: "prepare commit"
  • Changes: ["Added authentication endpoint", "Updated tests"]
  • Context: {"branch": "feature/auth"}

Frequently Asked Questions about git-helper

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

FAQPage Schema
How do I generate conventional commit messages for my feature branch?

You can generate conventional commit messages by providing the Skill with a list of your code changes and the branch context, which it analyzes to output a standardized, ready-to-use commit message.

What is the best way to prepare a pull request for code review?

The best way to prepare a pull request is to run this Skill with your feature changes to get a suggested branch name, recommended git commands, and a PR checklist to speed up code reviews.

Can I use this to enforce consistent git workflows across my software team?

Yes, you can use this to enforce consistent git workflows across your team by generating standardized commit messages and recommending branch naming conventions to maintain a clean project history.

How do I suggest a branch naming convention for new development tasks?

To suggest a branch naming convention for development tasks, the Skill evaluates your provided changes and context, such as a feature branch identifier, and outputs a recommended branch name.

What should I provide to get recommended git commands and next actions?

You should provide a description of the changes you made, the desired outcome, and the branch context to receive suggested git commands and actionable next steps for your workflow.