Automated summary
Generates a Conventional Commits message from staged changes and creates the git commit.
Strengths
- Reads the full staged diff, not just the --stat summary
- Mirrors the existing style by inspecting the last ten commits
- Pre-delivery checklist covers sensitive files (.env, keys), the 72-character subject limit, and imperative mood
- Clear prefix table for feat, fix, refactor, docs, test, chore, perf, style, and ci
Limitations
- Works only on already-staged changes; if nothing is staged it just prints git status
- Runs no tests or build checks before committing
- Does not automatically split a commit that bundles unrelated changes
Use it when your changes are already staged and you want a standardized commit message without drafting one yourself.
Avoid it if you expect the skill to stage files for you or to validate tests and builds before committing.
Security analysis
SafeThe skill uses Bash only for standard git inspection and commit commands (git diff, git log, git status, git commit). It does not execute destructive commands, contact external services, exfiltrate data, or disable safety mechanisms. The checklist even reminds the user to avoid committing sensitive files.
No concerns found
How this analysis is madeExamples
Commit my staged changes with a proper Conventional Commits message.I fixed the null pointer in the auth middleware — it's staged, please commit it.Fais un commit de ce qui est indexé, en suivant la convention Conventional Commits.name: commit description: Use when the user wants to commit changes, save work, or create a git commit message. disable-model-invocation: true allowed-tools: Bash
Generate a commit message and commit staged changes.
Steps
-
Check staged changes
git diff --cached --stat git diff --cached -
Check recent commit style
git log --oneline -10 -
Generate commit message following Conventional Commits:
| Prefix | When to Use | |--------|------------| |
feat:| New feature | |fix:| Bug fix | |refactor:| Code restructure, no behavior change | |docs:| Documentation only | |test:| Adding or fixing tests | |chore:| Build, deps, config changes | |perf:| Performance improvement | |style:| Formatting, whitespace | |ci:| CI/CD changes | -
Format rules
- Subject line: max 72 characters, imperative mood ("Add" not "Added")
- Body: wrap at 80 characters, explain WHY not WHAT
- If multiple changes: use bullet points in body
-
Commit
git commit -m "type: short description - Detail 1 - Detail 2" -
Show result
git log --oneline -1
Pre-Delivery Checklist
Before committing, verify:
- [ ]
git diff --cachedwas read (not just--stat) - [ ] Commit prefix matches the change type (feat/fix/refactor/etc.)
- [ ] Subject line is under 72 characters
- [ ] Subject uses imperative mood ("Add" not "Added")
- [ ] No sensitive files staged (.env, credentials, keys)
- [ ] No unrelated changes bundled in the same commit
- [ ] Body explains WHY if the change is non-obvious
If nothing is staged
Run git status and tell the user what files are available to stage.
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-with-conventional-commits-mryiqgst/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-with-conventional-commits-mryiqgst' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-with-conventional-commits-mryiqgst/download' --output '.skill-downloads/commit-with-conventional-commits-mryiqgst/SKILL.md.part' && mv '.skill-downloads/commit-with-conventional-commits-mryiqgst/SKILL.md.part' '.skill-downloads/commit-with-conventional-commits-mryiqgst/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.
Tools declared by the author (check availability in your agent): Bash
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-with-conventional-commits-mryiqgst/SKILL.md' && test -s '.skill-downloads/commit-with-conventional-commits-mryiqgst/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/commit-with-conventional-commits-mryiqgst' '.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-with-conventional-commits-mryiqgst'openskills read 'commit-with-conventional-commits-mryiqgst'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-with-conventional-commits-mryiqgst/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.