How do I install the Git Commit Helper skill?

Run npx skillmds@latest add tomevault-io/git-commit-helper-8 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 Git Commit Helper safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Helper?

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 Git Commit Helper free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commit Helper?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commit Helper by tomevault-io — Agent Skill

Name: Git Commit Helper
Author: tomevault-io

Git Commit Helper

Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commit Helper Skill

Instructions

Analyze the staged changes or diff to understand what was modified
Determine the type of change:
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Code style changes (formatting, no logic change)
- refactor: Code refactoring
- perf: Performance improvements
- test: Adding or updating tests
- chore: Maintenance tasks, build config, etc.
- ci: CI/CD changes
- build: Build system changes
Write a clear, concise subject line (50 chars or less)
Add a blank line, then detailed body if needed (wrap at 72 chars)
Reference issues/PRs when applicable
Use imperative mood: "Add feature" not "Added feature" or "Adds feature"
Follow conventional commits format: type(scope): subject

Examples

Input: "I added a new login button and fixed the validation bug" Output:

feat(auth): add login button to header

- Add new login button component to navigation header
- Implement click handler to open login modal
- Add styling to match design system

fix(validation): resolve email validation error

- Fix regex pattern for email validation
- Add test cases for edge cases
- Update error message to be more user-friendly

Closes #123

Input: "Updated the README and fixed some typos" Output:

docs: update README with installation instructions

- Add detailed installation steps for different platforms
- Include troubleshooting section
- Fix typos in existing documentation

Input: "Refactored the payment processing code" Output:

refactor(payments): improve payment processing logic

- Extract payment validation into separate function
- Simplify retry logic for failed transactions
- Improve error handling and logging
- Add unit tests for payment flow

BREAKING CHANGE: PaymentProcessor constructor now requires config object

Format Guidelines

Conventional Commits Format:

<type>(<scope>): <subject>

<body>

<footer>

Types:

feat: New feature for users
fix: Bug fix for users
docs: Documentation only
style: Formatting, missing semicolons, etc.
refactor: Code change that neither fixes bug nor adds feature
perf: Performance improvement
test: Adding missing tests
chore: Changes to build process or auxiliary tools

Best Practices:

Subject line: imperative, lowercase, no period
Body: explain what and why, not how
Footer: reference issues, breaking changes
Use present tense: "Fix bug" not "Fixed bug"

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: git-commit-helper-8description: Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions. Use when this capability is needed.---# Git Commit Helper Skill## Instructions1. Analyze the staged changes or diff to understand what was modified2. Determine the type of change: - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation changes - `style`: Code style changes (formatting, no logic change) - `refactor`: Code refactoring - `perf`: Performance improvements - `test`: Adding or updating tests - `chore`: Maintenance tasks, build config, etc. - `ci`: CI/CD changes - `build`: Build system changes3. Write a clear, concise subject line (50 chars or less)4. Add a blank line, then detailed body if needed (wrap at 72 chars)5. Reference issues/PRs when applicable6. Use imperative mood: "Add feature" not "Added feature" or "Adds feature"7. Follow conventional commits format: `type(scope): subject`## Examples**Input:** "I added a new login button and fixed the validation bug"**Output:**```feat(auth): add login button to header- Add new login button component to navigation header- Implement click handler to open login modal- Add styling to match design systemfix(validation): resolve email validation error- Fix regex pattern for email validation- Add test cases for edge cases- Update error message to be more user-friendlyCloses #123```**Input:** "Updated the README and fixed some typos"**Output:**```docs: update README with installation instructions- Add detailed installation steps for different platforms- Include troubleshooting section- Fix typos in existing documentation```**Input:** "Refactored the payment processing code"**Output:**```refactor(payments): improve payment processing logic- Extract payment validation into separate function- Simplify retry logic for failed transactions- Improve error handling and logging- Add unit tests for payment flowBREAKING CHANGE: PaymentProcessor constructor now requires config object```## Format Guidelines**Conventional Commits Format:**```<type>(<scope>): <subject><body><footer>```**Types:**- `feat`: New feature for users- `fix`: Bug fix for users- `docs`: Documentation only- `style`: Formatting, missing semicolons, etc.- `refactor`: Code change that neither fixes bug nor adds feature- `perf`: Performance improvement- `test`: Adding missing tests- `chore`: Changes to build process or auxiliary tools**Best Practices:**- Subject line: imperative, lowercase, no period- Body: explain what and why, not how- Footer: reference issues, breaking changes- Use present tense: "Fix bug" not "Fixed bug"---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lexicalninja) — claim your Tome and manage your conversions.

Frequently asked questions