How do I install the Generating Smart Commits skill?

Run npx skillmds@latest add bbgnsurftech/generating-smart-commits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Generating Smart Commits safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Generating Smart Commits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Generating Smart Commits free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Generating Smart Commits?

BbgnsurfTech (@bbgnsurftech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Generating Smart Commits by bbgnsurftech

Name: Generating Smart Commits
Rating: 4.2 (5 reviews)
Author: BbgnsurfTech

Generating Smart Commits

Use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.

BbgnsurfTech Updated Sep 10, 2026

File contents

Prerequisites

Before using this skill, ensure:

Git repository is initialized in {baseDir}
Changes are staged using git add
User has permission to create commits
Git user name and email are configured

Instructions

Analyze Staged Changes: Examine git diff output to understand modifications
Determine Commit Type: Classify changes as feat, fix, docs, style, refactor, test, or chore
Identify Scope: Extract affected module or component from file paths
Detect Breaking Changes: Look for API changes, removed features, or incompatible modifications
Format Message: Construct message following pattern: type(scope): description
Present for Review: Show generated message and ask for confirmation before committing

Output

Generates conventional commit messages in this format:

type(scope): brief description

- Detailed explanation of changes
- Why the change was necessary
- Impact on existing functionality

BREAKING CHANGE: description if applicable

Examples:

feat(auth): implement JWT authentication middleware
fix(api): resolve null pointer exception in user endpoint
docs(readme): update installation instructions

Error Handling

Common issues and solutions:

No Staged Changes

Error: "No changes staged for commit"
Solution: Stage files using git add <files> before generating commit message

Git Not Initialized

Error: "Not a git repository"
Solution: Initialize git with git init or navigate to repository root

Uncommitted Changes

Warning: "Unstaged changes detected"
Solution: Stage relevant changes or use git stash for unrelated modifications

Invalid Commit Format

Error: "Generated message doesn't follow conventional format"
Solution: Review and manually adjust type, scope, or description

Resources

Conventional Commits specification: https://www.conventionalcommits.org/
Git commit best practices documentation
Repository commit history for style consistency
Project-specific commit guidelines in {baseDir}/CONTRIBUTING.md

---name: generating-smart-commitsdescription: Use when generating conventional commit messages from staged git changes. Trigger with phrases like "create commit message", "generate smart commit", "/commit-smart", or "/gc". Automatically analyzes changes to determine commit type (feat, fix, docs), identifies breaking changes, and formats according to conventional commit standards.license: MIT---## PrerequisitesBefore using this skill, ensure:- Git repository is initialized in {baseDir}- Changes are staged using `git add`- User has permission to create commits- Git user name and email are configured## Instructions1. **Analyze Staged Changes**: Examine git diff output to understand modifications2. **Determine Commit Type**: Classify changes as feat, fix, docs, style, refactor, test, or chore3. **Identify Scope**: Extract affected module or component from file paths4. **Detect Breaking Changes**: Look for API changes, removed features, or incompatible modifications5. **Format Message**: Construct message following pattern: `type(scope): description`6. **Present for Review**: Show generated message and ask for confirmation before committing## OutputGenerates conventional commit messages in this format:```type(scope): brief description- Detailed explanation of changes- Why the change was necessary- Impact on existing functionalityBREAKING CHANGE: description if applicable```Examples:- `feat(auth): implement JWT authentication middleware`- `fix(api): resolve null pointer exception in user endpoint`- `docs(readme): update installation instructions`## Error HandlingCommon issues and solutions:**No Staged Changes**- Error: "No changes staged for commit"- Solution: Stage files using `git add <files>` before generating commit message**Git Not Initialized**- Error: "Not a git repository"- Solution: Initialize git with `git init` or navigate to repository root**Uncommitted Changes**- Warning: "Unstaged changes detected"- Solution: Stage relevant changes or use `git stash` for unrelated modifications**Invalid Commit Format**- Error: "Generated message doesn't follow conventional format"- Solution: Review and manually adjust type, scope, or description## Resources- Conventional Commits specification: https://www.conventionalcommits.org/- Git commit best practices documentation- Repository commit history for style consistency- Project-specific commit guidelines in {baseDir}/CONTRIBUTING.md

Frequently asked questions