commit-standards

Enforce structured commit messages and version bump rules for SDD projects.

39|3|Updated Nov 21, 2025

Search Tags:#git #changelog #versioning #documentation #commit #code-quality #best-practices

Ready to run

npx skills add https://github.com/LiorCohen/sdd --skill commit-standards-liorcohen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-standards
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/commit-standards
Command: npx skills add https://github.com/LiorCohen/sdd --skill commit-standards-liorcohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidelines for consistent, well-documented commits in SDD projects to maintain a clear project history, enable reliable changelogs, and simplify audits.

Core Features & Use Cases

Structured commit message formats (Action/Component: Description, bump to X.Y.Z) to standardize history.
Comprehensive guidelines for when to commit (every filesystem change, milestone artifacts, and task transitions) and how to document changes.
Includes a changelog workflow, verification checklist, and best-practice examples to improve traceability and collaboration.

Quick Start

Follow the standard whenever making changes: write a concise, structured commit message and update the changelog accordingly.

Frequently Asked Questions about commit-standards

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

FAQPage Schema

How do I format git commit messages for consistent project history?▼

Git commit messages use a structured format of Action/Component: Description, bump to X.Y.Z to ensure traceable changes and a coherent changelog across SDD projects. This standardizes history and simplifies audits.

What is the best way to maintain a reliable changelog from commits?▼

A reliable changelog uses a one-entry-per-commit policy aligned with changelog entries during every filesystem change. This ensures structured commit bodies and version bump rules map directly to traceable project milestones.

When should I commit changes in an SDD workflow?▼

In an SDD workflow, commit on every filesystem change, milestone artifact creation, and task transition. This includes spec creation, plan approvals, implementations, and verifications to maintain a traceable project history.

Does this commit standard require specific versioning rules for milestones?▼

Yes, this commit standard specifies explicit version bump rules for milestones, ensuring structured commit bodies and a one-entry-per-commit policy aligned with changelog entries for all SDD workflow artifacts.

Why does inconsistent documentation make code audits difficult?▼

Inconsistent documentation makes audits difficult because unstandardized commit histories prevent reliable changelog generation and obscure traceable changes. Applying a repeatable commit protocol enforces structured, coherent project documentation.