commit

Generate versioned commits with changelog updates and type checks.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill commit-liorcohen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/LiorCohen/sdd/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/LiorCohen/sdd --skill commit-liorcohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating commits that follow repository guidelines is error-prone and leads to inconsistent versioning and missing changelog entries.

Core Features & Use Cases

  • Enforces version bumps for relevant files and updates manifests during releases.
  • Validates and generates proper changelog entries in changelog/vX.md with a consistent format.
  • Guides the end-to-end workflow: analyze changes, run type checks, bump versions, and produce a standardized commit message.

Quick Start

Audit recent changes and generate a properly versioned commit with a corresponding changelog entry.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages and changelog updates for release management?

Automating git commit messages and changelog updates involves analyzing recent code changes, running type checks, bumping versions in manifest files, and generating standardized commit formats with corresponding changelog entries. This enforces repository compliance during release preparation.

How do I ensure my version bump includes a compliant changelog entry?

To ensure a version bump includes a compliant changelog entry, validate recent changes first, then update version files and manifests alongside generating a standardized entry in changelog/vX.md. This enforces a consistent format across versioned commits.

What is the best way to standardize commit messages during plugin development?

Standardizing commit messages during plugin development requires guiding the workflow end-to-end: auditing changes, validating types, bumping versions, and producing a formatted commit message. This prevents missing changelog entries and inconsistent versioning.

Does automated release management work without running type checks before committing?

Automated release management workflows typically require type checks before committing to ensure code validity. The process validates changes, bumps relevant versions, updates manifests, and generates the commit message only after preliminary checks pass.

Why do my manual git commits lead to inconsistent versioning and missing changelog entries?

Manual git commits lead to inconsistent versioning and missing changelog entries because human error often bypasses repository guidelines. Automating the workflow enforces version bumps, manifest updates, and standardized changelog formats to eliminate these errors.