commit

Enforce conventional commit messages and trigger automatic documentation updates.

1|Updated Feb 21, 2026

Search Tags:#automation #git #workflow #commit #policy #conventional-commit #docs-update

Ready to run

npx skills add https://github.com/kssumin/claude-playground --skill commit-kssumin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kssumin/claude-playground/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/kssumin/claude-playground --skill commit-kssumin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

수동으로 표준 커밋 메시지를 작성하고 변경 사항에 따라 자동으로 문서를 업데이트하는 번거로움을 제거합니다.

Core Features & Use Cases

Conventional commits 강제: 커밋 메시지가 규칙에 맞게 형식화됩니다.
변경 파일 기반 자동 Docs 업데이트: 파일 변경에 따라 문서가 자동으로 갱신됩니다.
리포지토리 워크플로우 대체: 시스템 기본 git 커맨드를 대신하는 지시를 제공합니다.

Quick Start

제목은 type: 간결한 설명 형식으로 작성하고 본문은 비워 두면 자동으로 문서 업데이트가 트리거된다.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce conventional commit messages in my git workflow?▼

Conventional commit enforcement works by requiring commit titles in the type: concise description format, which then automatically triggers documentation updates based on the changed files in the repository.

Can I automatically update documentation based on changed files in a git repository?▼

Yes, automatic documentation updates are triggered by file changes. When you commit with a properly formatted conventional commit message, the system regenerates downstream diagrams and docs for affected project boundaries like controllers and domains.

What is the conventional commit format needed to trigger automatic docs updates?▼

The conventional commit format requires a title structured as type: concise description. Leaving the body empty after writing the correctly formatted title will automatically trigger the documentation regeneration workflow.

Does this conventional commit enforcement work with software projects that have clear change boundaries?▼

Yes, it is specifically designed for software projects with clear change boundaries like controllers, domains, and infrastructure. These boundaries drive the deterministic generation of downstream diagrams and documentation updates.

Do I need a specific configuration file format to set up the automated commit and docs workflow?▼

You need a YAML frontmatter containing the name and description fields within the SKILL.md file. This configuration enables the deterministic commit and documentation regeneration workflows for your repository.