skills.rest
Awish021
Awish021COMMUNITY
Explore all skills by this author →
GitHub

conventional-commits

Generate Git commit messages adhering to the Conventional Commits specification.

10|1|Updated Jan 18, 2026
Search Tags:#git#version control#commit#conventional commits#code history
One-click install
npx skills add https://github.com/Awish021/opencode --skill conventional-commits-awish021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/Awish021/opencode/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/Awish021/opencode --skill conventional-commits-awish021

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you generate Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

  • Automated Commit Message Drafting: Creates commit messages based on staged code changes.
  • Enforces Commit Standards: Guides users to follow specific formatting rules for types, scopes, and bodies.
  • Use Case: After completing a new feature, use this Skill to draft a commit message like feat(auth): implement two-factor authentication.

Quick Start

Use the conventional-commits skill to draft a commit message for the staged changes.

Frequently Asked Questions about conventional-commits

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

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

To write conventional commit messages, you generate git commit text adhering to the Conventional Commits specification, enforcing imperative mood, specific type prefixes, and optional scope and body for standardized code history.

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

The conventional commits specification standardizes version control history by enforcing specific type prefixes and structures, enabling automated changelog generation and semantic versioning for software development workflows.

How do I format a git commit message for automated changelog generation?▼

Format git commit messages for automated changelog generation by applying conventional commits standards, using specific type prefixes like feat or fix, and including an optional scope and body for clarity.

Why does my conventional commit message need to use imperative mood?▼

Conventional commit messages use imperative mood to match git's internal commit history mechanics, ensuring standardized code history formatting that maintains clarity for automated changelog generation and semantic versioning.

Can I generate a conventional commit message with a specific scope like auth?▼

Yes, you can generate a conventional commit message with a specific scope like auth by applying optional scope parameters alongside type prefixes, resulting in structured messages such as feat(auth): implement two-factor authentication.

What are the limitations of using conventional commits for code history?▼

Limitations of conventional commits include strict adherence to specific type prefixes and imperative mood formatting, requiring consistent application across all git commits to successfully maintain standardized code history for automated semantic versioning.

Related Skills

Explore More Software Engineering Skills→
christopherlouetchristopherlouet
5

work-commit

Generate Conventional Commits commit messages from git diff outputs.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
ntluong95ntluong95

Git & Collaboration Standards

Enforce Git commit, branch, and pull request standards.

Community
Intermediate
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate