skills.rest
jovivaspo
jovivaspoCOMMUNITY
Explore all skills by this author →
GitHub

commit

Generate Git commit messages following the conventional commits specification.

Updated Aug 23, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/jovivaspo/base-agent-next-app --skill commit-jovivaspo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jovivaspo/base-agent-next-app/tree/main/skills/commit
Command: npx skills add https://github.com/jovivaspo/base-agent-next-app --skill commit-jovivaspo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of professional Git commit messages, ensuring consistency and adherence to best practices, which streamlines code reviews and project history management.

Core Features & Use Cases

  • Conventional Commits: Enforces the conventional commits specification for clear and structured commit messages.
  • Automated Formatting: Guides the user to select the correct commit type, scope, and provides a concise description.
  • Use Case: After completing a new feature, you can ask the AI to help you create a feat commit message that accurately describes the changes and their impact.

Quick Start

Use the commit skill to create a git commit for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I write a conventional commit message for my Git changes?▼

Conventional commit messages require selecting a type like feat or fix, defining a scope such as api or ui, and writing a concise descriptive title. This enforces structured Git history and streamlines code reviews.

How do I format the body of a Git commit message?▼

Formatting a Git commit body involves crafting bulleted points that describe the changes. This ensures adherence to character limits and avoids including granular implementation details in the title.

What is the conventional commits specification used for in version control?▼

The conventional commits specification standardizes Git commit messages by enforcing structured types and scopes. Automating this selection standardizes project history management and improves code review workflows.

Can I use conventional commits for both features and chores in Git?▼

Yes, conventional commits support both features and chores in Git. The automated selection process handles various commit types including feat, fix, and chore to accurately categorize different development tasks.

Does a conventional commit title need to exclude implementation details?▼

Yes, a conventional commit title must exclude implementation details. Crafting a descriptive title requires keeping it concise and within character limits, while saving specific implementation information for the bulleted body points.

Related Skills

Explore More Software Engineering Skills→
theodrosyimertheodrosyimer

conventional-commit

Generate commitlint-compliant conventional commit messages from staged diffs.

Community
Intermediate
KAIROS7-team3KAIROS7-team3

git-conventions

Standardizes Git commit messages, branch naming, and merge practices.

Official
Advanced
mkusakamkusaka
7

code-review-phase-0-gather-the-diff

Retrieve unified diffs from git repositories for code review.

Community
Basic
ThinkInAIXYZThinkInAIXYZ
6.2k

git-commit

Generate Conventional Commits messages with type, scope, subject, body, and footers.

Official
Basic