skills.rest
Yassimba
YassimbaCOMMUNITY
Explore all skills by this author →
GitHub

commit

Creates atomic git commits with test gates and Conventional Commits messages.

9|Updated Jul 17, 2026
Search Tags:#git#version control#commit#conventional commits#pre-commit hooks#atomic commits#test gate
One-click install
npx skills add https://github.com/Yassimba/loom --skill commit-yassimba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Yassimba/loom/tree/main/skills/commit
Command: npx skills add https://github.com/Yassimba/loom --skill commit-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing git commits often leads to mixed-concern changes, vague messages, and commits that break because tests were never run. This Skill enforces a disciplined commit workflow so every commit is atomic, tested, and clearly described. ## Core Features & Use Cases - Atomic staging: Stages files by explicit path only, splits diffs spanning multiple concerns into separate commits, and avoids sweeping in secrets like .env files. - Test gate: Runs the project's test suite before committing and blocks the commit when tests fail, routing failures to a bug-diagnosis workflow. - Conventional Commits drafting: Drafts subject and body messages in Conventional Commits format (feat, fix, refactor, etc.) based on the why of the staged diff, then confirms via a dropdown before committing. - Use Case: After finishing a feature, ask the agent to commit. It stages only the relevant files, runs the test suite, drafts feat(installer): add gateway runtime extraction, and commits only after your approval. ## Quick Start Use the commit skill to stage my current changes and create a commit with a proper message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a good git commit message?▼

Use Conventional Commits format: a type prefix like feat, fix, or refactor, followed by a lowercase imperative subject of 20-72 characters. Add a body only when the subject cannot carry the why, with terse bullets grouped under headings like Added, Changed, or Fixed.

How do I split a large git change into atomic commits?▼

Unstage unrelated paths with git restore --staged, then stage and commit one concern at a time. Each commit should contain exactly one concern so it can be reviewed, reverted, or cherry-picked independently.

Should I run tests before committing code?▼

Yes. Running the project's test suite before committing catches failures early, since pre-commit hooks typically fail on the same issues. A red test suite should block the commit and route to bug diagnosis instead.

What happens when a pre-commit hook fails?▼

Fix the underlying cause in the code rather than bypassing the hook. Lint issues get fixed in code, type errors get corrected, and test failures go through diagnosis. Bypass flags like --no-verify and suppression comments stay unused.

Why avoid git add -A or git add . when staging?▼

Blanket staging commands sweep in unintended files such as .env files and credentials. Stage by explicit path only so each commit contains exactly the files belonging to one concern.

Related Skills

Explore More Software Engineering Skills→
lbusselllbussell

commit

Generate atomic Git commits with imperative subject lines and explanatory bodies.

Community
Intermediate
basicmachines-cobasicmachines-co
4.0k

pull-request

Manages the full GitHub pull request lifecycle from branch hygiene through merge gating.

Official
Advanced
silcamsilcam

commit

Create conventional git commits and resolve pre-commit hook failures in TypeScript repositories.

Official
Intermediate
ilonatommyilonatommy
3

commit-squashing

Consolidate multiple Git commits into a single commit using rebase, reset, or merge strategies.

Community
Intermediate