Agent skill
commit
Generates git commit messages following Conventional Commits 1.0.0 specification with semantic types (feat, fix, etc.), optional scope, and breaking change annotations. Use when committing code changes or creating commit messages. Triggers on phrases like 'commit', 'commit and push', 'make a commit', 'git commit', or when commit is part of a compound action (e.g., 'bump version and commit').
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/commit-neversight-skills-feed-2
SKILL.md
Conventional Commit Generator
Workflow
-
Run
git statusandgit diff HEADto analyze changes -
Stage files: user-specified only, or
git add -Afor all -
Commit using HEREDOC format:
bashgit commit -m "$(cat <<'EOF' <type>(<scope>): <description> EOF )" -
Output:
<hash> <subject>
DO NOT: Modify code, push (unless asked), amend without request
Format
<type>[scope][!]: <description>
Types: feat, fix, perf, refactor, style, test, docs, build, ci, revert, chore
Subject: Imperative mood ("Add" not "Added"), capitalize first letter, no period, ~50 chars (max 72)
Scope: Optional noun for affected area (e.g., auth, api, parser)
Breaking changes: Add exclamation mark before colon: feat(api)!: Remove deprecated endpoints
Issue references: Use footer: Closes #123 or Fixes #456
Body (when needed)
Add body for non-trivial changes. Explain what and why, not how. Wrap at 72 chars.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?