Automated summary
Groups local changes into coherent commits and writes descriptive commit messages, only when the user explicitly asks for it.
Strengths
- Splits the diff into logical commit units instead of fragmented micro-commits
- Uses partial staging to keep only the relevant hunks
- Writes a short imperative summary with an optional rationale-focused body
- Filters out debug code and commented-out instrumentation before committing
Limitations
- Never fires on its own: an explicit commit request is required
- Does not cover pushing, opening PRs, or rewriting history
- Mentions no test or hook verification before committing
Use it when a local diff needs to become a set of clean, well-named commits.
Avoid it when you want to publish changes (push/PR) or alter existing history.
Security analysis
SafeThe skill only instructs reviewing diffs and creating git commits after explicit user request. It does not invoke shells, exfiltrate data, disable safeguards, or perform destructive operations. Although it implicitly uses git tooling, that is a normal, low-risk local development action.
No concerns found
How this analysis is madeExamples
Commit my changes, splitting them into logical commits with clear messages.Stage only the files related to the auth fix and commit them with a descriptive message.I've finished the refactor — review the uncommitted diff and commit it in coherent chunks.name: commit description: Stage and commit local changes in logical chunks with high-quality commit messages. disable-model-invocation: true
Commit Changes
When to use
- User explicitly requests creating commit(s)
Instructions
- Review uncommitted diff and untracked files.
- Group related edits into coherent commit units.
- Stage appropriately (partial staging when necessary).
- Write descriptive commit messages:
- short imperative summary
- optional body focused on rationale
Rules
- Never commit unless user explicitly asks
- Exclude debug code and commented-out instrumentation
- Prefer fewer coherent commits over fragmented micro-commits
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-changes-in-logical-chunks-mrzxuqj0/download' --output '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md.part' && mv '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md.part' '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md' && test -s '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0' '.claude/skills/commit'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0'openskills read 'commit-changes-in-logical-chunks-mrzxuqj0'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/commit-changes-in-logical-chunks-mrzxuqj0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.