skills.rest
yasudaProduct
yasudaProductCOMMUNITY
Explore all skills by this author →
GitHub

commit-helper

Enforce typed Git commit messages and PR creation workflows.

1|Updated Feb 3, 2026
Search Tags:#git#workflow#commit#branching#code-review#pull-request
One-click install
npx skills add https://github.com/yasudaProduct/chord-chart --skill commit-helper-yasudaproduct
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/yasudaProduct/chord-chart/tree/main/.claude/skills/commit-helper
Command: npx skills add https://github.com/yasudaProduct/chord-chart --skill commit-helper-yasudaproduct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git commit messages and PR workflows to improve traceability and collaboration within the ChordBook project.

Core Features & Use Cases

  • Commit Message Format: Enforces the <type>: <subject> pattern with types like feat, fix, docs, style, refactor, test, chore.
  • PR Creation Guidance: Provides PR title/body templates and commands to create PRs consistently.
  • Branch Naming: Enforces conventional branch prefixes such as feature/, fix/, docs/, and refactor/.
  • Step-by-step Workflow: Guides developers through git status, git diff, git add, git commit, git push, and gh pr create.

Quick Start

Write a properly formatted commit message using the <type>: <subject> format and then open a PR following the PR template.

Frequently Asked Questions about commit-helper

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

FAQPage Schema
How do I enforce consistent Git commit messages across my team?▼

You can enforce consistent Git commit messages by applying a typed format using the <type>: <subject> pattern with prefixes like feat, fix, docs, style, refactor, test, and chore to improve traceability and code review efficiency.

What is the standard workflow for creating a pull request from a feature branch?▼

The standard pull request workflow involves executing step-by-step Git commands including git status, git diff, git add, git commit, git push, and finally gh pr create, while following predefined PR title and body templates for consistency.

How do I name Git branches for bug fixes and new features?▼

You should name Git branches using conventional prefixes such as feature/, fix/, docs/, and refactor/ to categorize work clearly and maintain project traceability during collaborative development.

Can I use this workflow for documentation updates and chore tasks?▼

Yes, this workflow supports everyday software development tasks including documentation updates and chore tasks by utilizing the specific docs and chore commit types within the standardized messaging format.

What is the best way to streamline PR creation and improve code review efficiency?▼

The best way to streamline PR creation and improve code review efficiency is to enforce standardized PR templates alongside consistent commit messaging and branch naming conventions for deterministic, step-by-step workflows.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
yocxy2yocxy2

land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

Community
Advanced
sandgardenhqsandgardenhq
130

go-code-review

Review Go code against official style guides and static analysis guidelines.

Official
Basic
vanman2024vanman2024
3

Git Workflows

Standardize git workflows with commit templates, branch helpers, and hook scripts.

Community
Basic