Commit Helper
Skill Verified ActiveHelps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
To help developers write well-formatted Git commit messages efficiently, adhering to the Conventional Commits specification, and improving project history clarity.
Features
- Generates Conventional Commits messages
- Validates commit message format
- Provides guidance on types, scopes, and formatting
- Includes examples for various scenarios
- Integrates with Git workflow for commit generation
Use Cases
- When a user asks to commit changes
- When a user requests to write or format git commit messages
- To enforce a standardized commit message format
- To improve the clarity and consistency of Git history
Non-Goals
- Performing Git operations beyond commit message generation
- Managing merge conflicts or rebasing
- Automating the entire Git commit process without user review
Installation
npx skills add charon-fan/agent-playbookRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedSimilar Extensions
Unslop Commit
100Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why" isn't obvious from the subject. Use when user says "humanize commit", "de-slop commit message", "make this commit sound human", "/unslop-commit", "/commit", "write a commit", or pastes a draft commit to clean up. Auto-triggers when staging changes.
Ctx Doctor
100Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Git Commit
99Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
Caveman Commit
98Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Commit Changes
97Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the most recent commit, or reviewing staged changes before committing.
Commit
95Create well-formatted commits with conventional commit messages and emoji