Automated summary
Provides guidance for crafting Git commit messages following conventional commit format and best practices.
Strengths
- Step-by-step guidance for conventional commit format
- Analyzes staged changes to generate relevant messages
- Supports multiple commit types and optional scopes
Limitations
- May require manual intervention for complex changes
- Does not automatically handle issue references or breaking changes
When creating or editing Git commit messages to ensure clarity and consistency.
For projects using a non-conventional commit format or when automatic generation is not desired.
Security analysis
SafeThe skill provides only textual guidance for commit messages and does not execute any commands that could compromise system integrity or exfiltrate data.
No concerns found
How this analysis is madeExamples
Analyze the staged changes in this repository and suggest a conventional commit message.Explain the conventional commit format and list the allowed types with examples.Here's my draft commit message: 'fixed bug in login'. Help me rewrite it as a conventional commit.name: git-commit-helper description: Provides expert guidance for Git commit messages, including conventional commit formatting and best practices. Use when creating or editing Git commit messages. allowed-tools:
- Bash
- Read
- Write
- Edit
- Glob
- Grep
Overview
Provides expert guidance for creating conventional commit messages that follow industry best practices. Helps generate clear, consistent commit messages by analyzing staged changes.
Conventional Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Commit Types
- feat: A new feature for the user
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that don't affect code meaning (white-space, formatting, missing semi-colons, etc.)
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies
- ci: Changes to CI configuration files and scripts
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Rules
- Type is mandatory: Choose the most appropriate type from the list above
- Scope is optional: Add in parentheses to specify what part of codebase (e.g.,
feat(auth):,fix(api):) - Description:
- Use imperative mood ("add" not "added" or "adds")
- Don't capitalize first letter
- No period at the end
- Keep under 72 characters
- Body is optional: Provide context about what and why, not how
- Footer is optional: Reference issues, note breaking changes
Examples
Simple commit
feat: add user authentication
With scope
fix(auth): prevent token expiration on refresh
With body
refactor(api): restructure endpoint handlers
Move handler logic into separate service layer to improve
testability and maintain single responsibility principle.
Breaking change
feat(api): change authentication response format
BREAKING CHANGE: API now returns user object instead of just token.
Update all API consumers to handle new response structure.
Multiple footers
fix(database): resolve connection pool exhaustion
Fixes #123
Closes #456
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/git-commit-helper-mmk3nhj6/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/git-commit-helper-mmk3nhj6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-commit-helper-mmk3nhj6/download' --output '.skill-downloads/git-commit-helper-mmk3nhj6/SKILL.md.part' && mv '.skill-downloads/git-commit-helper-mmk3nhj6/SKILL.md.part' '.skill-downloads/git-commit-helper-mmk3nhj6/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/git-commit-helper-mmk3nhj6/SKILL.md' && test -s '.skill-downloads/git-commit-helper-mmk3nhj6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-commit-helper' && cp -R '.skill-downloads/git-commit-helper-mmk3nhj6' '.claude/skills/git-commit-helper'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/git-commit-helper-mmk3nhj6'openskills read 'git-commit-helper-mmk3nhj6'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/git-commit-helper-mmk3nhj6/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.