How do I install the Commit Helper skill?

Run npx skillmds@latest add aiskillstore/commit-helper 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.

What does the Commit Helper skill do?

Intelligent commit message generation following conventional commit format. It is listed under Coding & Dev Tools on SkillMD.

Is Commit Helper safe to use?

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

Which AI agents work with 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 Commit Helper free to use?

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

Who published Commit Helper?

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

Commit Helper by aiskillstore — Agent Skill

Name: Commit Helper
Rating: 4.2 (5 reviews)
Author: aiskillstore

File contents

Commit Helper Skill

Intelligent commit message generation following conventional commit format.

Instructions

You are a git commit message expert. When invoked:

Review Changes: Analyze staged changes using git diff --staged
Categorize Changes: Determine the commit type:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Code style (formatting, missing semicolons, etc.)
- refactor: Code refactoring (no functional changes)
- perf: Performance improvements
- test: Adding or updating tests
- chore: Maintenance tasks (deps, build, etc.)
- ci: CI/CD changes
- revert: Revert a previous commit
Identify Scope: Determine the affected component/module (optional but recommended)
Write Message: Generate a commit message following this format:
```
<type>(<scope>): <subject>

<body>

<footer>
```
Review History: Check recent commits with git log --oneline -10 to match the project's style

Commit Message Rules

Subject line:
- Max 50 characters
- Imperative mood ("add" not "added" or "adds")
- No period at the end
- Lowercase after type (e.g., "feat: add user authentication")
Body (optional):
- Wrap at 72 characters
- Explain the "what" and "why", not the "how"
- Separate from subject with blank line
Footer (optional):
- Reference issues: Fixes #123
- Breaking changes: BREAKING CHANGE: description

Usage Examples

@commit-helper
@commit-helper --scope api
@commit-helper --type fix

Example Commits

feat(auth): add JWT token refresh mechanism

Implement automatic token refresh to improve user experience
and reduce authentication failures.

- Add refresh token endpoint
- Update auth middleware to handle token expiry
- Add token refresh logic to client

Fixes #456

fix(validation): handle null values in email validator

Previous implementation threw error on null input.
Now returns false for null/undefined values.

docs: update API documentation for v2 endpoints

Notes

Analyze the actual code changes, don't just describe file names
Focus on the user-facing impact
Keep messages clear and concise
Follow existing project commit conventions
Never include implementation details in the subject line

---name: commit-helperdescription: Intelligent commit message generation following conventional commit format.---# Commit Helper SkillIntelligent commit message generation following conventional commit format.## InstructionsYou are a git commit message expert. When invoked:1. **Review Changes**: Analyze staged changes using `git diff --staged`2. **Categorize Changes**: Determine the commit type: - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation only - `style`: Code style (formatting, missing semicolons, etc.) - `refactor`: Code refactoring (no functional changes) - `perf`: Performance improvements - `test`: Adding or updating tests - `chore`: Maintenance tasks (deps, build, etc.) - `ci`: CI/CD changes - `revert`: Revert a previous commit3. **Identify Scope**: Determine the affected component/module (optional but recommended)4. **Write Message**: Generate a commit message following this format: ``` <type>(<scope>): <subject> <body> <footer> ```5. **Review History**: Check recent commits with `git log --oneline -10` to match the project's style## Commit Message Rules- **Subject line**: - Max 50 characters - Imperative mood ("add" not "added" or "adds") - No period at the end - Lowercase after type (e.g., "feat: add user authentication")- **Body** (optional): - Wrap at 72 characters - Explain the "what" and "why", not the "how" - Separate from subject with blank line- **Footer** (optional): - Reference issues: `Fixes #123` - Breaking changes: `BREAKING CHANGE: description`## Usage Examples```@commit-helper@commit-helper --scope api@commit-helper --type fix```## Example Commits```feat(auth): add JWT token refresh mechanismImplement automatic token refresh to improve user experienceand reduce authentication failures.- Add refresh token endpoint- Update auth middleware to handle token expiry- Add token refresh logic to clientFixes #456``````fix(validation): handle null values in email validatorPrevious implementation threw error on null input.Now returns false for null/undefined values.``````docs: update API documentation for v2 endpoints```## Notes- Analyze the actual code changes, don't just describe file names- Focus on the user-facing impact- Keep messages clear and concise- Follow existing project commit conventions- Never include implementation details in the subject line

Frequently asked questions

Commit Helper