skills.rest
Jonathan0823
Jonathan0823COMMUNITY
Explore all skills by this author →
𝕏@GuinnJo1GitHub

git-commit

Generate git commit messages following the conventional commits format.

7|Updated Feb 5, 2026
Search Tags:#git#commit#best-practices#code-review#version-control#conventional-commits
One-click install
npx skills add https://github.com/Jonathan0823/opencode-config --skill git-commit-jonathan0823
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Jonathan0823/opencode-config/tree/main/skills/git-commit
Command: npx skills add https://github.com/Jonathan0823/opencode-config --skill git-commit-jonathan0823

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams enforce conventional commits to ensure a readable, standardized git history, improving traceability and code review.

Core Features & Use Cases

  • Generate commit messages that follow the conventional commits format: <type>(<scope>): <subject>.
  • Enforce single-responsibility commits and provide concise bodies when needed.
  • Support typical development workflows, including features, fixes, documentation updates, and refactors.

Quick Start

Use this skill to craft a conventional commit message for a new login feature: feat(auth): add OAuth2 login.

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write conventional commit messages for git?▼

Conventional commit messages follow the format <type>(<scope>): <subject>. This skill standardizes your git commits by enforcing this structure to ensure a readable and traceable version control history.

Why use conventional commits for version control and code review?▼

Conventional commits improve code review and traceability by enforcing single-responsibility commits. This standardizes git history across projects, making feature development and bug fixes easier to track.

What is the correct format for a feature or bug fix commit?▼

The correct format is <type>(<scope>): <subject>. Use feat for features and fix for bug fixes, adding an optional scope and a concise body to clarify the changes.

Can I use this for documentation updates and refactoring?▼

Yes, this skill supports typical development workflows including documentation updates and refactors. It generates standardized commit messages for these tasks using the conventional commits format.

Should I include a body in my conventional commit message?▼

Yes, you should include a concise body when needed. The skill encourages single-responsibility commits with meaningful bodies to provide context for complex changes.

Related Skills

Explore More Software Engineering Skills→
swissarmyhammerswissarmyhammer
15

commit

Create Git commits following the Conventional Commits specification.

Official
Intermediate
richardadonnellrichardadonnell
45

changelog-automation

Generate changelogs from commit history using Conventional Commits and Keep a Changelog format.

Community
Intermediate
kirvinkirvin

commit

Stage Git changes and create conventional commit messages with preflight checks.

Community
Intermediate
ClubMediterraneeClubMediterranee
4

git-commit

Analyze diffs and generate Conventional Commits messages with auto-detected type and scope.

Official
Intermediate