conventional-commit

Enforces Conventional Commits policy for atomic, changelog-ready git commit messages.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill conventional-commit-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/conventional-commit
Command: npx skills add https://github.com/islamu-ngo/Event --skill conventional-commit-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle with inconsistent commit messages, oversized umbrella commits, and changelogs that mix internal refactors with user-facing changes. This Skill enforces a strict Conventional Commits policy so every commit is an atomic, reviewable unit with correct scopes, trailers, and changelog classification. ## Core Features & Use Cases - Atomic Commit Slicing: Clusters dirty working trees into smallest releasable vertical slices, keeping generated code with its triggering change and splitting unrelated work. - Scope & Trailer Enforcement: Applies a canonical scope registry (e.g., registration, database, ci) and requires Changelog: skip / Changelog-Reason: trailers on internal commits and BREAKING CHANGE: footers on breaking work. - Safe Staging Protocols: Provides path-limited git commit recipes for shared checkouts so unrelated staged changes never leak into a commit. - Use Case: An engineer finishes a registration feature plus a test-hardening fix on a shared checkout; the Skill guides splitting them into two scoped commits with correct trailers and verifies the resulting commit file lists. ## Quick Start Ask the assistant to review the current git working tree and produce a conventional commit plan with staged file lists and commit messages.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I write a conventional commit message for a feature?▼

Use the format type(scope): benefit-led subject, choosing a capability scope like registration or ticketing rather than a code layer. Write the subject in imperative mood describing the user or operator benefit, and keep the commit to one smallest releasable outcome.

How do I split a large dirty git working tree into atomic commits?▼

Cluster files by priority: vertical feature slices first, then technical fixes, test hardening, build config, and governance docs. Describe each candidate commit in one benefit-led sentence and remove every file not required to make that sentence true.

What scopes are allowed in conventional commit messages?▼

Allowed scopes come from a canonical registry: public capability scopes like events, registration, ticketing, and discovery, plus engineering scopes like ci, database, testing, and release. Layer scopes such as api, persistence, dto, or client are forbidden.

When does a commit need a Changelog skip trailer?▼

Internal nonbreaking commits of type test, build, ci, refactor, style, or internal docs and fix must carry both Changelog: skip and a non-empty Changelog-Reason trailer. This keeps them out of public release notes while documenting why.

How do I commit safely when unrelated files are already staged?▼

Inspect the index with git status and git diff --cached, stage only your owned files, then use git commit --only with explicit paths. Verify the result with git show --name-only, and never commit a file containing another contributor's hunks.