Automated summary
Generates commit messages using the Conventional Commits format and creates commits from staged changes.
Strengths
- Structures messages clearly with type and optional scope
- Automates adherence to commit best practices
- Analyzes staged changes to determine the appropriate type
Limitations
- Requires changes to be staged first
- May not accurately capture the intent behind complex changes
- Only adds a body when needed, potentially omitting important context
Use this skill to standardize commit messages in a project following Conventional Commits.
Avoid it if you prefer manually writing highly detailed messages or if your project uses a different commit format.
Security analysis
SafeThe skill only instructs to run 'git diff --staged' to read staged changes, which is a safe, read-only operation. No destructive, exfiltrating, or obfuscated commands are used.
No concerns found
How this analysis is madeExamples
Write a commit message for the staged changes using Conventional Commits format.Create a commit with type 'feat' and scope 'auth' for the staged changes.Review the staged changes and suggest an appropriate Conventional Commit message.name: commit description: Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes.
Commit Messages
Use Conventional Commits format.
Format
<type>(<scope>): <description>
[optional body]
Types
feat: User-facing features or behavior changes (must change production code)fix: Bug fixes (must change production code)docs: Documentation onlystyle: Code style/formatting (no logic changes)refactor: Code restructuring without behavior changetest: Adding or updating testschore: CI/CD, tooling, dependency bumps, configs (no production code)
Scopes
Optional. Use when it adds clarity. Examples: ui, api, state, auth.
Examples
feat(search): add infinite scroll to results
fix(album): correct image path validation
refactor(state): simplify album loading machine
chore: add husky pre-commit hooks
docs: update API documentation
test: add E2E tests for login flow
Instructions
- Run
git diff --stagedto see staged changes - Analyze the changes and determine the appropriate type
- Write a concise description (under 72 characters)
- Add body only if the "why" isn't obvious from the description
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/conventional-commit-messages-mmlj2oon/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/conventional-commit-messages-mmlj2oon' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/conventional-commit-messages-mmlj2oon/download' --output '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md.part' && mv '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md.part' '.skill-downloads/conventional-commit-messages-mmlj2oon/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/conventional-commit-messages-mmlj2oon/SKILL.md' && test -s '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/conventional-commit-messages-mmlj2oon' '.claude/skills/commit'Cursor
test -f '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md' && test -s '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/commit' && cp -R '.skill-downloads/conventional-commit-messages-mmlj2oon' '.cursor/skills/commit'Codex
test -f '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md' && test -s '.skill-downloads/conventional-commit-messages-mmlj2oon/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/commit' && cp -R '.skill-downloads/conventional-commit-messages-mmlj2oon' '.agents/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/conventional-commit-messages-mmlj2oon'openskills read 'conventional-commit-messages-mmlj2oon'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/conventional-commit-messages-mmlj2oon/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.