skills.rest
shidax-corp
shidax-corpOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Commit Message

Generate conventional git commit messages and issue-based branch names.

Updated Aug 12, 2025
Search Tags:#git#workflow#commit#branch#conventional-commits#ai-assisted
One-click install
npx skills add https://github.com/shidax-corp/kintone-authenticator --skill commit-message
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Message
Source: https://github.com/shidax-corp/kintone-authenticator/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/shidax-corp/kintone-authenticator --skill commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces conventional commit messages and consistent branch naming, reducing ambiguity in project history and easing code reviews.

Core Features & Use Cases

  • Conventional Commit Guidance: Suggests types like feat/fix and aligns with project conventions.
  • Branch Naming: Proposes descriptive branch names based on task and issue numbers.
  • Workflow Compliance: Ensures PRs reference issues and use consistent labels in descriptions.

Quick Start

Create a new feature branch named 'issue-123/add-auth' and commit with message 'feat(auth): add login flow' following the project conventions.

Frequently Asked Questions about Commit Message

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

FAQPage Schema
How do I write conventional commit messages for git?▼

Conventional commits follow a structured format with type, scope, and description: type(scope): description. Common types include feat, fix, docs, style, refactor, perf, and test. This standardizes project history and simplifies code reviews.

What's the proper way to name git branches?▼

Branch names should follow the pattern issue-<number>/<short-description>, for example issue-123/add-auth. This ties branches to issues and makes their purpose immediately clear in your workflow.

Why use conventional commits in my workflow?▼

Conventional commits reduce ambiguity in project history, enable automated changelog generation, and make code reviews faster by establishing a consistent, searchable commit format across your team.

How do scope prefixes work in commit messages?▼

Scope prefixes categorize commits by affected area, such as feat(auth), fix(api), or docs(readme). Common scopes include kintone, chrome, lib, components, and docs, helping reviewers quickly identify what part of the codebase changed.

Can I commit directly to the main branch?▼

No. Conventional workflow mandates creating a feature or fix branch named issue-<number>/<short-description> instead of committing directly to main, ensuring all changes go through review and traceability.

Does this apply to refactors and other commit types?▼

Yes. Beyond feat and fix, conventional commits support refactor, style, perf, test, chore, and design types across all codebase changes, maintaining consistent messaging for all modifications.

Related Skills

Explore More Software Engineering Skills→
eavichayeavichay

git-feature

Create Git feature branches and isolated worktrees with sequential or timestamped numbering.

Community
Advanced
davidabeyerdavidabeyer
13

shipping-worktree

Automate shipping Git worktree changes to the main branch.

Official
Advanced
skyasu2skyasu2
2

security-audit-workflow

Automate pre-deployment security audits for Next.js/Supabase CI pipelines.

Community
Advanced
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic