commit

Enforce Conventional Commits format and branch naming guidelines.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/monobaselabs/monobase-js --skill commit-monobaselabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/monobaselabs/monobase-js/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/monobaselabs/monobase-js --skill commit-monobaselabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes commit messages and branch naming to improve code review speed and release traceability.

Core Features & Use Cases

  • Enforces the Conventional Commits format for all commits.
  • Provides consistent branch naming guidelines (feature/, fix/, chore/, docs/, refactor/).
  • Improves PR hygiene and release notes generation with predictable history.

Quick Start

Create a new feature branch and commit using a conventional commit message when changes are ready.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commits format in my git workflow?▼

This skill enforces conventional commits and branch naming guidelines across feature, bugfix, docs, and chore branches to standardize version history and improve release traceability.

What branch naming conventions should I use for feature and bugfix branches?▼

This skill enforces the Conventional Commits format for all commits and provides consistent branch naming guidelines including feature/, fix/, chore/, docs/, and refactor/ to standardize version history.

How does standardizing commit messages improve PR hygiene and release notes?▼

This skill standardizes commit messages and branch naming to improve code review speed and release traceability, applying conventional commits to meet release-process standards.

Can I apply conventional commits and branch naming during pre-commit checks?▼

This skill applies to developer workflows during pre-commit or post-change review phases, enforcing conventional commits and branch naming to satisfy release-process standards and ensure consistency.

Do I need any dependencies to start using conventional commits and branch naming?▼

This skill requires no dependencies; simply create a new feature branch and commit using a conventional commit message when changes are ready to enforce commit formatting and branch naming disciplines.