dqx-conventional-commit

Create conventional commits conforming to DQX's commitizen validation rules.

Updated Aug 23, 2026

Search Tags:#git #types #commit-message #conventional-commit #scopes #subject-length #commitizen

Ready to run

npx skills add https://github.com/nampham2/dqx --skill dqx-conventional-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dqx-conventional-commit
Source: https://github.com/nampham2/dqx/tree/main/.opencode/skills/dqx-conventional-commit
Command: npx skills add https://github.com/nampham2/dqx --skill dqx-conventional-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create conventional commits that satisfy DQX's commitizen validation rules, helping teams maintain a clean, auditable project history and reducing review friction.

Core Features & Use Cases

Provides a clear template for commit messages with type, scope, and subject
Enforces the required parts and optional parts (body and footer) to ensure consistency
Includes guidelines and examples for all commit types and scopes to accelerate adoption

Quick Start

Create a conventional commit that adheres to DQX standards.

Frequently Asked Questions about dqx-conventional-commit

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

FAQPage Schema

How do I write a conventional commit message that passes commitizen validation?▼

Standardized commit messages enforce required types, scopes, and subject lengths to maintain a clean project history. Applying consistent commit guidelines across software teams reduces code review friction and ensures traceable messaging.

What components are required in a conventional commit template for DQX projects?▼

A conventional commit template requires a type, scope, and subject. Optional body and footer sections provide additional context, ensuring consistency and traceability across software projects.

Does this conventional commit Skill work across different software project teams?▼

Yes, this approach applies conventional commit rules across various software projects and teams. Providing clear guidelines and examples for all commit types and scopes accelerates adoption and standardization.

Are there guidelines for commit subject length and scopes in conventional commits?▼

Yes, guidelines enforce specific subject lengths and define appropriate scopes for conventional commits. These rules standardize messaging, satisfy commitizen validation, and reduce review friction for development teams.

Why should software teams enforce conventional commit standards?▼

Enforcing conventional commit standards helps teams maintain a clean, auditable project history and reduces review friction. Standardized types, scopes, and subjects ensure traceable messaging across the entire codebase.