Validate staged commit messages against type(scope): title format rules.
npx skills add https://github.com/sendo-kakeru/family-photo --skill commit-sendo-kakeru
Please help me install this Agent Skill. Skill: commit Source: https://github.com/sendo-kakeru/family-photo/tree/main/.claude/skills/commit Command: npx skills add https://github.com/sendo-kakeru/family-photo --skill commit-sendo-kakeru
ステージングした変更を一貫した形式でコミットする際の手間を減らし、メッセージ規約の遵守を自動的に促します。
ステージングした変更に対して、規約に沿った新しいコミットを作成してください。
High-intent search queries and answers about installing and using this skill.
To enforce conventional commit formatting for staged Git changes, this Skill validates the type(scope): title structure, enforces a 70-character subject limit, and ensures a blank line before the body to guarantee message compliance.
Allowed commit types for conventional commit messages include feat, fix, docs, style, perf, test, refactor, chore, and revert, explicitly defining the intent of your staged changes.
To structure a Git commit message correctly, separate the subject line from the body with a blank line, keep the subject under 70 characters, and use the body to explain the Why behind the code changes.
This commit message validator does not support custom types; it applies a predefined type list including feat, fix, docs, style, perf, test, refactor, chore, and revert to standardize your commit history.
The best way to document breaking changes in a conventional commit is by following the structural guidelines provided by this Skill, which integrates breaking change notifications into the body to ensure clear communication.
im9Generate a conventional commit message and commit staged files.
t0labAnalyze Conventional Commits to draft changelogs and create release commits and tags.
JohnRobert-OlanoAutomate Husky pre-commit hook setup with lint-staged for formatting, type checks, and tests.
voidrotGenerate changelogs and release notes from commit history and tags.
