Automated summary
Formats Git commit messages following the Conventional Commits specification with type, optional scope, and description.
Strengths
- Clear and standardized commit message structure
- Simplifies automatic changelog generation
- Integrates well with semantic versioning
- Encourages concise, imperative descriptions
Limitations
- Requires team discipline to be effective
- May be overly formal for very simple changes
- Optional scope can be confusing if misused
Use this format when you want to standardize commit messages for release automation and changelog generation.
Avoid imposing it on personal or highly informal projects where flexibility is preferred.
Security analysis
SafeThis skill provides guidelines for commit message formatting; it does not execute any code or interact with system resources, posing no security risk.
No concerns found
How this analysis is madeExamples
Write a conventional commit message for adding a login feature with email and password authentication.Generate a commit message following conventional commits for a bug fix that prevents crash on empty input array.Create a conventional commit message for renaming user endpoints as a breaking change.name: conventional-commits description: > Format commit messages following the Conventional Commits specification: type, optional scope, and a concise description. tags:
- git
- standards metadata: version: "1.0"
Conventional Commits
Write commit messages that follow the Conventional Commits specification.
Instructions
When creating a git commit, format the message as:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types:
| Type | When to use |
|------|-------------|
| feat | A new feature |
| fix | A bug fix |
| docs | Documentation-only changes |
| style | Formatting, whitespace — no logic changes |
| refactor | Code restructuring with no feature or fix |
| test | Adding or updating tests |
| chore | Build scripts, tooling, dependency updates |
| perf | Performance improvements |
| ci | CI/CD configuration changes |
Rules:
- The description must be lowercase and imperative ("add feature", not "Added feature").
- Keep the first line under 72 characters.
- Use the body to explain why, not what — the diff shows what changed.
- Add
BREAKING CHANGE:in the footer (or!after the type) for breaking changes.
Examples
feat(auth): add password reset flow
Implements the forgot-password endpoint and email
verification step.
Closes #42
fix: prevent crash on empty input array
refactor(api)!: rename user endpoints
BREAKING CHANGE: /users/list is now /users and
/users/get/:id is now /users/:id.
Notes
- If the project already has a commit convention, follow that instead.
- Scope is optional — use it when the change is clearly limited to one module or area.
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-commits-mm5t8c9o/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-commits-mm5t8c9o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/conventional-commits-mm5t8c9o/download' --output '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md.part' && mv '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md.part' '.skill-downloads/conventional-commits-mm5t8c9o/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-commits-mm5t8c9o/SKILL.md' && test -s '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/conventional-commits' && cp -R '.skill-downloads/conventional-commits-mm5t8c9o' '.claude/skills/conventional-commits'Cursor
test -f '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md' && test -s '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/conventional-commits' && cp -R '.skill-downloads/conventional-commits-mm5t8c9o' '.cursor/skills/conventional-commits'Codex
test -f '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md' && test -s '.skill-downloads/conventional-commits-mm5t8c9o/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/conventional-commits' && cp -R '.skill-downloads/conventional-commits-mm5t8c9o' '.agents/skills/conventional-commits'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-commits-mm5t8c9o'openskills read 'conventional-commits-mm5t8c9o'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-commits-mm5t8c9o/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.