skills.rest
akashic-devkit
akashic-devkitOFFICIAL
Explore all skills by this author →
GitHub

commit-convention

Enforce Conventional Commits format for Git commit messages in the akashic-devkit monorepo.

2|1|Updated Sep 19, 2025
Search Tags:#git#code review#commit#conventional commits#commitlint#monorepo
One-click install
npx skills add https://github.com/akashic-devkit/akashic-devkit --skill commit-convention-akashic-devkit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-convention
Source: https://github.com/akashic-devkit/akashic-devkit/tree/main/.claude/skills/commit-convention
Command: npx skills add https://github.com/akashic-devkit/akashic-devkit --skill commit-convention-akashic-devkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a consistent and understandable commit message format, improving code review clarity and automating changelog generation.

Core Features & Use Cases

  • Enforces Conventional Commits: Ensures all commit messages adhere to a strict type(scope): subject format.
  • Scope Mapping: Provides clear guidelines for selecting the correct scope (web, cli, config, root) based on the changed directory.
  • Type Selection Guidance: Offers a table to help choose the appropriate commit type (feat, fix, chore, etc.) based on the intent of the change.
  • Use Case: When preparing to commit changes to the packages/cli directory, use this skill to ensure your commit message follows the feat(cli): add new command format.

Quick Start

Use the commit-convention skill to format your commit message for a change in the apps/web directory.

Frequently Asked Questions about commit-convention

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

FAQPage Schema
How do I format git commit messages using conventional commits in a monorepo?▼

Format git commit messages in a monorepo using the strict `type(scope): subject` syntax. Select a scope like `web` or `cli` based on the changed directory, and choose a type like `feat` or `fix` based on the change intent.

What is the conventional commits format for code review clarity?▼

The conventional commits format for code review clarity is `type(scope): subject`. It uses predefined types such as `feat`, `fix`, `chore`, and scopes like `web`, `cli`, `config`, and `root` to standardize commit intent.

How do I choose the correct scope for a git commit in a monorepo?▼

Choose the correct git commit scope in a monorepo by matching the changed directory to predefined scopes: `web`, `cli`, `config`, or `root`. This maps changes directly to their affected package for clear tracking.

Does commitlint work with conventional commits for automated validation?▼

Commitlint works with conventional commits to provide automated validation. It enforces the `type(scope): subject` format, ensuring all git commit messages adhere to the specification before integration.

When do I need to use the conventional commits specification for git commits?▼

You need the conventional commits specification for git commits when you want to improve code review clarity and automate changelog generation. It enforces a consistent `type(scope): subject` format across all commit operations.

What are the limitations of using predefined types and scopes for commit messages?▼

The limitation of using predefined commit message types and scopes is strict adherence to the `type(scope): subject` format. You must select from defined types like `feat` or `fix` and scopes like `web` or `cli`, limiting freeform messages.

Related Skills

Explore More Software Engineering Skills→
diriendirien
19

commitlint

Validate commit messages against the Conventional Commits specification in Node.js git environments.

Community
Intermediate
daniel-heydari-devdaniel-heydari-dev

changelog-generation

Generate changelogs and enforce semantic versioning from conventional commits.

Community
Intermediate
theodrosyimertheodrosyimer

conventional-commit

Generate commitlint-compliant conventional commit messages from staged diffs.

Community
Intermediate
FelipePepeFelipePepe

rule-gitflow

Enforce standardized Git workflows with Conventional Commits and Husky hooks.

Community
Intermediate