skills.rest
Simon-YHKim
Simon-YHKimCOMMUNITY
Explore all skills by this author →
GitHub

commit

Creates Conventional Commits-style git commits by analyzing staged and unstaged changes.

Updated Apr 5, 2026
Search Tags:#git#version control#commit#conventional commits#staging#commit message
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill commit-simon-yhkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill commit-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted git commit messages is tedious and often inconsistent across a team. This Skill inspects your working tree, determines the correct commit type, and produces a Conventional Commits-style message that matches your repository's existing log style. ## Core Features & Use Cases - Repository State Inspection: Runs git status, git diff, and git log in parallel to understand what changed and match the repo's existing commit style. - Conventional Commits Formatting: Automatically classifies changes as feat, fix, docs, refactor, test, chore, perf, or style, and drafts a type(scope): subject message with an optional why-focused body. - Safe Staging Practices: Stages specific files by name instead of git add -A, and refuses to commit .env files, credentials, or large binaries. - Use Case: After finishing a bug fix across three files, ask for a commit and receive a properly scoped message like fix(auth): handle expired token refresh without manually reviewing the diff or recalling the format. ## Quick Start Ask the assistant to commit the current changes in this repository following the Conventional Commits style.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a Conventional Commits message?▼

Use the format type(scope): subject, where type is feat, fix, docs, refactor, test, chore, perf, or style. Keep the subject under 72 characters in imperative mood, and add an optional body explaining why the change was made rather than what changed.

How do I stage and commit specific files in git?▼

Stage files individually by name with git add <file> instead of git add -A, then commit with a HEREDOC for multi-line messages. This prevents accidentally committing .env files, credentials, or large binaries.

What commit types exist in Conventional Commits?▼

The main types are feat for new features, fix for bug fixes, docs for documentation, refactor for code changes that neither fix bugs nor add features, test for test updates, chore for build and tooling, perf for performance, and style for formatting.

What should I do when a pre-commit hook fails?▼

Fix the underlying issue reported by the hook and create a new commit. Never use --no-verify to skip hooks, and do not amend existing commits unless explicitly requested.

Does this skill push commits to a remote repository?▼

No, it only creates local commits and verifies success with git status afterward. Pushing to a remote is never performed unless the user explicitly asks for it.

Related Skills

Explore More Software Engineering Skills→
valentinuuiuiuvalentinuuiuiu

verification-loop

Run tests, linters, type checks, security scans, and diff reviews on code commits.

Community
Intermediate
santychuycomsantychuycom

ship

Analyze diffs, create atomic conventional commits, push, and open pull requests.

Official
Advanced
vikisingh23vikisingh23
4

changelog

...

Community
Intermediate
tobihagemanntobihagemann
399

stage

Stage specific files or code hunks for a Git commit.

Community
Basic