git-commit-helper

Generate conventional commit messages without scopes based on staged changes. Use when the user asks for commit message help, has staged changes, or is about to commit.

Git Commit Helper (No Scope)

Generate conventional commit messages without a scope.

When to use this skill

  • The user asks for a commit message
  • Staged changes exist
  • The user is about to run git commit
  • The user mentions conventional or semantic commits

Workflow

  1. Review staged files and the staged diff.
  2. Identify the primary change type and any breaking changes.
  3. Draft a commit message using the format below.
  4. Provide a short rationale and ask if the user wants adjustments.

Commit format (no scope)

<type>: <subject>

<body>

<footer>

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Formatting only (no logic change)
  • refactor: Code restructuring without behavior change
  • perf: Performance improvements
  • test: Test additions or fixes
  • build: Build system or tooling changes
  • ci: CI/CD pipeline changes
  • chore: Maintenance tasks

Subject checklist

  • Imperative mood ("add", "fix", "update")
  • 50-72 characters max
  • No trailing period
  • Describes what and why, not how
  • Lowercase after the type

Breaking changes

If the change is breaking, include a footer:

BREAKING CHANGE: <what changed and how to migrate>

Examples

Feature

feat: add jwt authentication for api requests

- implement token validation middleware
- add login and refresh endpoints

Closes #42

Fix

fix: prevent memory leak in user list

Clean up subscriptions when the component unmounts.

Refactor

refactor: extract repository layer for database access

No functional changes. Improves testability and separation.

Breaking change

feat: update user api response structure

BREAKING CHANGE: response is now { data, metadata }.

Output expectations

  • Provide the recommended commit message in full.
  • Explain the chosen type and any breaking change rationale.