skills.rest
hkw2028
hkw2028COMMUNITY
Explore all skills by this author →
GitHub

commit

Create logical Conventional Commits for in-scope Git changes without pushing.

Updated Sep 17, 2026
Search Tags:#git#version control#commit#conventional commits#code history#staging#pre-commit hooks
One-click install
npx skills add https://github.com/hkw2028/toy-project --skill commit-hkw2028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/hkw2028/toy-project/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/hkw2028/toy-project --skill commit-hkw2028

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a messy working tree into clean, reviewable Git history is tedious and error-prone: unrelated changes get lumped together, other people's work gets swept in, and secrets can slip into commits. This Skill inspects the current status and diff, then creates well-scoped Conventional Commits for only the changes owned by the current request. ## Core Features & Use Cases - Logical commit splitting: Groups related changes (e.g., a behavior plus its tests) into independent Conventional Commits that can be reverted or cherry-picked cleanly. - Ownership and safety guardrails: Leaves other agents' or pre-existing changes unstaged, and excludes credentials, .env files, and private keys unless explicitly approved. - Hook compliance: Honors pre-commit hooks, repairs failures caused by the current change, and never bypasses hooks or pushes to the remote. - Use Case: After finishing a login feature with tests plus an unrelated README typo fix, ask to commit; the Skill creates separate conventional commits for the feature and the docs fix, then reports the resulting hashes. ## Quick Start Ask the assistant to commit your current changes as logical Conventional Commits without pushing to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit only some of my changed files in Git?▼

The Skill inspects git status and the diff, then stages and commits only the files owned by your current request. Unrelated or pre-existing changes, including edits made by other agents, are left unstaged and reported in the summary.

How do I split unrelated changes into separate commits?▼

It groups changes by concern so each commit can be understood, reverted, or cherry-picked independently. A behavior and the tests that establish it stay together, while unrelated fixes like documentation typos become separate Conventional Commits.

Does this commit skill push to the remote repository?▼

No, it never pushes. It only creates local commits and reports the resulting hashes and subjects, leaving the remote untouched so you can push or open a pull request separately.

Will Git commits include .env files or credentials?▼

No. Environment files, service account keys, and other secrets are excluded from commits unless you explicitly confirm a specific file is safe and intended for version control. Sensitive files left out are flagged in the report.

What happens when a pre-commit hook fails?▼

The Skill runs repository hooks through the normal commit flow and treats a failure as evidence to fix. It repairs failures caused by the current change and retries, never bypassing hooks with a no-verify option.

Related Skills

Explore More Software Engineering Skills→
jporrejporre
6

b3-git-commit

Analyze Git diffs and create conventional commits with a clean working tree.

Community
Intermediate
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
cartridge-ggcartridge-gg
80

pre-commit-check

Run Husky pre-commit hooks for format, lint, and test checks.

Official
Intermediate
mjun0812mjun0812
1

git-commit

Review current changes and commit them with Conventional Commits formatted messages.

Community
Basic