skills.rest
johnmog
johnmogCOMMUNITY
Explore all skills by this author →
GitHub

smart-commit

Generate concise commit messages and create feature branches from main or master.

Updated Aug 27, 2026
Search Tags:#git#developer tools#code review#workflow automation#commit#branching
One-click install
npx skills add https://github.com/johnmog/dotfiles --skill smart-commit-johnmog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smart-commit
Source: https://github.com/johnmog/dotfiles/tree/main/.copilot/skills/smart-commit
Command: npx skills add https://github.com/johnmog/dotfiles --skill smart-commit-johnmog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the git commit process by ensuring concise, clear commit messages and automatically creating feature branches when committing from main/master, preventing direct commits to critical branches.

Core Features & Use Cases

  • Automated Branching: Creates feature branches (e.g., johnmog-area-change) when committing from main or master.
  • Concise Commit Messages: Generates commit messages under 52 characters, following best practices (imperative mood, lowercase, no prefixes).
  • Use Case: When you have made several changes and want to commit them without cluttering the main branch, this skill will create a new branch for your changes and generate a descriptive commit message.

Quick Start

Use the smart-commit skill to commit your staged changes with an automatically generated message and branch if necessary.

Frequently Asked Questions about smart-commit

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

FAQPage Schema
How do I automate git commit messages and prevent direct commits to main?▼

To automate git commit messages and prevent direct commits to main, this skill analyzes staged changes to generate concise messages and automatically creates a feature branch when committing from main or master.

What is the best practice for git commit message length and format?▼

Git commit message best practices involve using imperative mood, lowercase letters, and no prefixes, keeping the message under 52 characters for clear and concise project history.

How do I automatically create a feature branch from master when committing changes?▼

To automatically create a feature branch from master when committing changes, the workflow detects commits staged on main or master and creates a descriptively named branch before applying the commit.

Can I generate descriptive branch names automatically from staged git changes?▼

Yes, you can generate descriptive branch names automatically from staged git changes by analyzing the diff to create names formatted like 'username-area-change' for clear tracking.

Does this git workflow automation tool require any external dependencies?▼

No, this git workflow automation tool requires no external dependencies, functioning entirely within your existing git environment to automate branching and commit message generation.

Related Skills

Explore More Software Engineering Skills→
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
hojinzshojinzs
16

push

Publish verified local commits to a remote Git branch with pre-push validation.

Community
Intermediate
queen-of-codequeen-of-code
8

git-workflow

Standardize Git workflows with conventional commits and branch protection rules.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic