skills.rest
kang8
kang8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Create git commits from staged changes with branch naming and validation.

2|Updated May 25, 2021
Search Tags:#automation#git#workflow#commit#branching#branch-prefix
One-click install
npx skills add https://github.com/kang8/.dotfiles --skill commit-kang8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kang8/.dotfiles/tree/main/claude/.claude/skills/commit
Command: npx skills add https://github.com/kang8/.dotfiles --skill commit-kang8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of creating git commits from the currently staged changes, ensuring compliance with project conventions and reducing manual decision-making.

Core Features & Use Cases

  • Sanity checks on staged changes (git status, git diff --staged, recent commits, current branch).
  • Branch decision logic based on CLAUDE.md rules and history to determine feature/bugfix branching needs.
  • Automatic branch creation with proper prefixes and naming when required.
  • Drafting commit messages that mirror the project's recent style and conventions.
  • Safe commit execution using a controlled, user-verified process; no automatic staging or amends.
  • Verification and reporting of the resulting branch and commit.

Quick Start

Instruct the AI to commit the currently staged changes following the project's conventions.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits to follow project conventions?▼

To automate git commits, the Skill reads staged changes and CLAUDE.md rules to draft messages and create feature/bugfix branches. It ensures branch naming, message drafting, and pre-commit validation align with your project's recent history and conventions.

How do I create a feature or bugfix branch before committing staged changes?▼

Creating a feature or bugfix branch is handled by branch decision logic based on CLAUDE.md rules and recent git history. It automatically determines the correct branch prefix and naming convention required before executing the commit.

Can I use this to generate commit messages that match my recent git history?▼

Yes, you can generate commit messages that mirror your project's recent style. The Skill analyzes recent commits and project conventions to draft appropriate messages based on the currently staged changes.

Does the commit automation automatically stage files or amend previous commits?▼

No, the commit automation does not automatically stage files or amend commits. It executes a safe, user-verified process using only currently staged changes to ensure controlled commit creation without modifying existing history.

What do I need to set up before automating my git workflow?▼

Before automating your git workflow, you need staged changes and a project configured with CLAUDE.md rules. The Skill relies on these conventions and recent git history to determine branching needs and draft compliant commit messages.

Related Skills

Explore More Software Engineering Skills→
muklesmukles

git-commit

Create a conventional git commit from staged or unstaged changes.

Community
Advanced
cdcooncecdcoonce

gitlab-cli

Manage GitLab repositories, issues, merge requests, and CI/CD pipelines via glab terminal commands.

Community
Intermediate
cropsggcropsgg
15

pre-commit-setup

Install Husky and configure lint-staged for staged-file checks.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

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

Community
Basic