Skill

commit-summary

Generates conventional commit messages from staged Git changes by reviewing diffs, categorizing as feat/fix/refactor/docs/test/chore, and formatting as type(scope): description. Use before committing.

Git

Bash

git-workflow

npx claudepluginhub shipshitdev/skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generate meaningful commit messages based on staged changes.

Supporting Assets

plugin.json

SKILL.md

Similar Skills

ui-ux-pro-max

70.8k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

51.8k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

competitive-landscape

32.9k

Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.

startup-business-analyst

Stats

Stars21

Forks2

Last CommitApr 21, 2026

Actions

View Source View Plugin View on GitHub View README

Commit Summary

Generate meaningful commit messages based on staged changes.

Workflow

Step 1: Review Changes

git status
git diff --staged
git log --oneline -5

Step 2: Analyze Changes

Categorize:

feat: New feature
fix: Bug fix
refactor: Code restructuring
docs: Documentation only
test: Adding/updating tests
chore: Maintenance tasks

Step 3: Generate Message

Format: type(scope): short description

What changed
Why it changed (if not obvious)

Step 4: Review

Ensure message:

Accurately describes changes
Follows project conventions
Is concise but complete

Guidelines

Start with type (feat, fix, refactor, etc.)
Include scope if applicable
Use imperative mood ("Add" not "Added")
Keep first line under 72 chars
Explain why, not just what

Examples

feat(auth): add password reset flow
fix(api): handle null response from external service
refactor(utils): extract date formatting to shared helper
docs: update API endpoint documentation

What NOT to Do

Vague messages ("fix stuff", "update code")
Too long first lines
Missing context for non-obvious changes
Committing unrelated changes together