Automated summary
Generates concise commit messages conforming to project conventions after automatically staging all changes and running pre-commit checks (formatting, linting, tests).
Strengths
- Ensures consistent commit message style
- Automates pre-commit verification
- Stages all changes automatically
- Uses imperative mood without conventional commit prefixes
Limitations
- Requires a Rust/Cargo project structure
- Cannot handle complex merge commits or interactive rebases
- Limited to specific toolchain (cargo fmt, clippy, test)
Use when committing changes in a Rust project that follows standard formatting and linting practices.
Do not use for non-Rust projects, or when you need to selectively stage files or write longer, more detailed commit bodies.
Security analysis
CautionThe skill uses powerful shell commands (git, cargo) for code quality enforcement and automated committing. While not destructive, it could stage unintended files or commit without user review, posing a moderate risk of accidental exposure or bad commits.
- •Automatically stages all changes with `git add -A`, potentially including unintended files.
- •Commits immediately after checks pass without user confirmation, which could inadvertently commit sensitive data.
Examples
Commit all my changes with the message following the project convention.I have some unstaged changes. Run the pre-commit checks and commit everything.Stage all changes, fix any clippy warnings, and commit.name: commit description: Generate commit messages following project conventions. Use when committing changes or reviewing staged files. allowed-tools: Bash(git:*), Bash(cargo *), Read, Edit, Glob, Grep
Commit Message Generator
Instructions
- Run
git statusto check for all changes (staged, unstaged, untracked) - If there are unstaged or untracked files, run
git add -Ato stage all changes - Run
git diff --stagedto see what will be committed - If no changes to commit, inform the user and stop
Pre-commit Checks
-
Run lint and test checks before committing:
- Run
cargo fmt --checkto check formatting - Run
cargo clippy -- -D warningsto check for lint errors - Run
cargo testto run tests
- Run
-
If any checks fail:
- For formatting issues: Run
cargo fmtto auto-fix - For clippy warnings: Read the affected files and fix the issues
- For test failures: Investigate and fix the failing tests
- After fixes, run
git add -Ato stage the fixes - Re-run the failed checks to verify fixes
- For formatting issues: Run
-
Once all checks pass, generate a commit message following the rules below
-
Run
git commit -m "message"immediately (no confirmation needed)
Format
- Line 1: Summary (max 50 chars, imperative mood)
- Line 2: Blank
- Line 3+: Description (optional, explain what and why)
Rules
- Write in English
- Use imperative mood: "Add", "Fix", "Change" (not "Added", "Fixed")
- NO prefixes like feat:, fix:, docs:
- Be specific, avoid vague messages
Examples
❌ Bad
- Fix
- Bug fix
- Various changes
✅ Good
- Change audio capture buffer size to 20ms
- Add retry logic for P2P connection failures
- Remove unused audio codec parameters
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-message-generator-mmh8qr7d/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-message-generator-mmh8qr7d' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/commit-message-generator-mmh8qr7d/download' --output '.skill-downloads/commit-message-generator-mmh8qr7d/SKILL.md.part' && mv '.skill-downloads/commit-message-generator-mmh8qr7d/SKILL.md.part' '.skill-downloads/commit-message-generator-mmh8qr7d/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(git:*), Bash(cargo *), Read, Edit, Glob, Grep
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-message-generator-mmh8qr7d/SKILL.md' && test -s '.skill-downloads/commit-message-generator-mmh8qr7d/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/commit-message-generator-mmh8qr7d' '.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-message-generator-mmh8qr7d'openskills read 'commit-message-generator-mmh8qr7d'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-message-generator-mmh8qr7d/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.