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.

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

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

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

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

Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin