🎯

commit-helper

🎯Skill

from nodnarbnitram/claude-code-extensions

VibeIndex|
What it does

Generates clear, conventional git commit messages by analyzing staged changes and recommending structured, descriptive commit formats.

πŸ“¦

Part of

nodnarbnitram/claude-code-extensions(19 items)

commit-helper

Installation

Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add github:nodnarbnitram/claude-code-extensions
Install PluginInstall plugin from marketplace
/plugin install cce-core@cce-marketplace
Install PluginInstall plugin from marketplace
/plugin install cce-kubernetes@cce-marketplace # For Kubernetes development
Install PluginInstall plugin from marketplace
/plugin install cce-cloudflare@cce-marketplace # For Cloudflare Workers/AI
Install PluginInstall plugin from marketplace
/plugin install cce-esphome@cce-marketplace # For ESPHome IoT

+ 6 more commands

πŸ“– Extracted from docs: nodnarbnitram/claude-code-extensions
12Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.

Overview

# Commit Helper

Generate well-structured commit messages following conventional commit format.

Instructions

  1. Run git diff --staged to see staged changes
  2. Analyze the changes to understand:

- What files were modified

- What type of change (feat, fix, refactor, docs, etc.)

- The scope/component affected

  1. Generate a commit message with:

- Summary line under 50 characters

- Type prefix (feat, fix, docs, refactor, test, chore)

- Optional scope in parentheses

- Detailed body explaining what and why

Commit Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • refactor: Code restructuring without behavior change
  • test: Adding or updating tests
  • chore: Maintenance tasks

Best Practices

  • Use present tense ("Add feature" not "Added feature")
  • Explain what and why, not how
  • Keep summary concise but descriptive
  • Reference issue numbers when applicable

Example Output

```

feat(auth): add OAuth2 support for GitHub login

  • Implement OAuth2 flow with PKCE
  • Add token refresh mechanism
  • Store tokens securely in encrypted storage

Closes #123

```