skills.rest
tkdn
tkdnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Generate Conventional Commits with staging and branch safety checks.

Updated Feb 7, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/tkdn/dotfiles --skill commit-tkdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/tkdn/dotfiles/tree/main/dot_claude/skills/commit
Command: npx skills add https://github.com/tkdn/dotfiles --skill commit-tkdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create logical, well-structured Git commits that adhere to the Conventional Commits specification, ensuring clarity and consistency in your version control history.

Core Features & Use Cases

  • Conventional Commits: Automatically formats commit messages according to the <type>[optional scope]: <description> structure.
  • Commit Planning: Guides you through analyzing changes, planning commit granularity, and presenting a commit plan for approval.
  • Safety Checks: Warns if you are about to commit directly to a main or master branch.
  • Use Case: When you've completed a new feature, use this Skill to stage your changes, write a descriptive commit message like feat(auth): implement user login, and ensure your commit history is clean and informative.

Quick Start

Use the commit skill to stage all changes and create a new commit with the message "feat: add new user profile page".

Frequently Asked Questions about commit

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

FAQPage Schema
What's the best way to organize staged files into logical Git commits?▼

This Skill analyzes your staged files and guides you through planning commit granularity. It presents a structured commit plan for your approval before execution, ensuring your Git history remains clean and logically organized.

Does this commit tool warn me before committing to a protected branch?▼

Yes, this Skill includes safety checks that warn you if you are about to commit directly to a main or master branch. This prevents accidental commits to protected branches in your version control workflow.

Can I generate a commit plan for approval before staging changes?▼

Yes, this Skill guides you through analyzing changes and planning commit granularity. It presents a structured commit plan for your approval before staging files and executing the final Git commits.

How do I structure a feature commit message for code review?▼

To structure a feature commit for code review, use the Conventional Commits format like `feat(auth): implement user login`. This Skill automatically generates these descriptive messages to ensure informative version control history.

When do I need to use the Conventional Commits specification?▼

You need the Conventional Commits specification when you want logical, well-structured Git commits that ensure clarity and consistency. This Skill automates that formatting process for your version control history.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

git-commit

Create convention-aware git commit messages with logical change grouping.

Community
Intermediate
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
bennybennisonbennybennison

git-commit-discipline

Enforce consistent git commit messages and clean branch history.

Community
Intermediate
phucle297phucle297

caveman-commit

Generate concise conventional commit messages for Git repositories.

Community
Intermediate