Skills Guide

Formatted conventional commit

VerifiedSafe

Creates Git commits following the conventional commits specification, using proper types (feat, fix, refactor, etc.) and formatting the message with an optional scope and body. Helps maintain a clear and standardized commit history across a project.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#git#conventional-commits#commit-message#version-control#code-quality

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Creates a well-formatted git commit following the Conventional Commits specification.

Strengths

  • Automates commit message formatting
  • Adheres to industry standards (Conventional Commits)
  • Improves repository history readability
  • Simplifies changelog generation

Limitations

  • Does not handle complex merge or history rewrite scenarios
  • No advanced semantic analysis of code changes
  • May require manual tuning for very detailed messages
When to use it

When you need to create a commit with a structured message compliant with conventions, especially in projects with automated releases.

When not to use it

For trivial changes where a simple message suffices, or if you prefer to write the full commit message manually.

Security analysis

Safe
Quality score93/100

The skill only uses git commands (status, diff, commit) locally with no destructive or exfiltrating actions. It does not involve arbitrary code execution or network operations beyond what git inherently does.

No concerns found

How this analysis is made

Examples

Simple commit with type and description
commit feat(auth): add login endpoint
Commit from staged changes with suggestion
commit fix: correct user validation error handling
Detailed commit with body and footer
commit refactor(hooks): extract useAuth logic into separate hook

name: commit description: Create a well-formatted conventional commit with proper message user-invocable: true argument-hint: [commit type or description] allowed-tools: Bash

Create a git commit following conventional commits specification.

Commit Types

  • feat: New feature
  • fix: Bug fix
  • refactor: Code refactoring
  • test: Adding tests
  • docs: Documentation
  • style: Formatting (no code change)
  • perf: Performance improvement
  • chore: Maintenance tasks

Process

  1. Run git status to see changes
  2. Run git diff --staged to review staged changes
  3. If no staged changes, suggest files to stage
  4. Generate commit message based on changes:
    • Use conventional commit format: type(scope): description
    • Keep subject line under 72 characters
    • Use imperative mood ("add" not "added")
    • Include body for complex changes

Commit Message Format

type(scope): short description

[optional body with more details]

[optional footer with breaking changes or issue references]

Examples

# Feature
git commit -m "feat(auth): add OAuth2 login with Google provider"

# Bug fix
git commit -m "fix(api): handle null response from external service"

# Refactor
git commit -m "refactor(hooks): extract useAuth logic into separate hook"

If argument provided: $ARGUMENTS

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 files

This 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.md

From the root of a test project, save the file as .skill-downloads/formatted-conventional-commit-mm8o5255/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/formatted-conventional-commit-mm8o5255' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/formatted-conventional-commit-mm8o5255/download' --output '.skill-downloads/formatted-conventional-commit-mm8o5255/SKILL.md.part' && mv '.skill-downloads/formatted-conventional-commit-mm8o5255/SKILL.md.part' '.skill-downloads/formatted-conventional-commit-mm8o5255/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/formatted-conventional-commit-mm8o5255/SKILL.md' && test -s '.skill-downloads/formatted-conventional-commit-mm8o5255/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/commit' && cp -R '.skill-downloads/formatted-conventional-commit-mm8o5255' '.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 installation
openskills install './.skill-downloads/formatted-conventional-commit-mm8o5255'

openskills read 'formatted-conventional-commit-mm8o5255'

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 sync

Manual 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/formatted-conventional-commit-mm8o5255/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.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

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.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

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.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot