skills.rest
SkinnnyJay
SkinnnyJayCOMMUNITY
Explore all skills by this author →
𝕏@gravyskyyGitHub

commit

Groups changed files into atomic commits using conventional commit format.

2|Updated Feb 15, 2026
Search Tags:#git#code review#version control#commit#conventional commits#staging#atomic commits
One-click install
npx skills add https://github.com/SkinnnyJay/simpill-utils --skill commit-skinnnyjay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SkinnnyJay/simpill-utils/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/SkinnnyJay/simpill-utils --skill commit-skinnnyjay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often dump unrelated changes into a single commit or write inconsistent commit messages, making history hard to review, revert, and audit. This Skill analyzes staged work and splits it into logical, atomic commits following the conventional commit format. ## Core Features & Use Cases - Logical Grouping: Runs git status and git diff to analyze changed files and group them by logical change before committing. - Conventional Commit Format: Enforces the type(scope): summary pattern with types like feat, fix, chore, refactor, docs, and test. - Safety Rules: Blocks committing .env files, credentials, or secrets, and requires lint and typecheck to pass first. - Use Case: After finishing a feature that touched three packages, ask the assistant to commit your work and receive separate commits like feat(async.utils): add retry logic and chore(deps): bump next to 14.2.1. ## Quick Start Ask the assistant to review your staged changes and create atomic conventional commits for each logical group.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split staged changes into multiple commits?▼

Run git status and git diff --staged to review all changes, then group files by logical change and stage each group separately with git add before committing. Each commit should contain exactly one logical change for a clean, revertable history.

What is the conventional commit format?▼

Conventional commits use the pattern type(scope): summary, where type is feat, fix, chore, refactor, docs, or test, scope names the affected area, and the summary is imperative present tense under 72 characters. Example: fix(api): handle null in schedule-runs endpoint.

How do I write a good commit message summary?▼

Write the summary in present tense imperative mood and keep it under 72 characters. Prefix it with the correct type and scope, such as feat(async.utils): add retry logic to polling manager, so the change is scannable in git log.

Should I run lint and typecheck before committing?▼

Yes, run npm run lint and npm run typecheck before committing to catch style and type errors early. This prevents broken code from entering the repository history and failing CI later.

What files should never be committed to git?▼

Never commit .env files, credentials, API keys, or other secrets to a repository. Add them to .gitignore and use environment variable management instead, since committed secrets persist in history even after deletion.

Related Skills

Explore More Software Engineering Skills→
BrunoAMSilvaBrunoAMSilva

git-commit

Generate Conventional Commits messages from repository diffs and stage files.

Community
Intermediate
leonardoacostaleonardoacosta

merge-to-main

Review and merge a delivery branch into main with local quality gates and exact-SHA protection.

Community
Advanced
SynkraAISynkraAI
3.1k

aiox-quality-gates

Runs lint, typecheck, test, and pre-push quality gates for AIOX projects.

Official
Basic
laicluselaicluse
4

commit-all-the-things

Groups all uncommitted git changes into logical commits with descriptive messages.

Official
Intermediate