Standardizing commit messages is critical for traceability and automation in multi-agent/multi-developer projects.
Currently, commit messages may vary in format, making it difficult to generate accurate changelogs or determine version bumps automatically.
The kano-commit-convention-skill provides a standard way to enforce the KCC-STCC (Subsystem + Type + Ticket) convention.
Goal
Provide a drop-in skill that:
Enforces commit conventions at the source (Git hooks).
Automates release artifacts (Changelog, Versioning) based on commit history.
Educates agents and developers on the KCC-STCC format.
Non-Goals
Replacing the version control system itself (supports Git, but methodology is VCS-agnostic).
Enforcing workflows outside of commit message formatting (e.g., branching strategies).
Approach
We will implement this skill via three main pillars:
Commit Linting: A commit-msg hook and linter script to validate messages against the KCC-STCC regex, including ticket existence checks.
Changelog: A generator script that parses valid commits and produces a grouped Markdown changelog.
Versioning: A bumper script that suggests semantic version updates (Major/Minor/Patch) based on commit types.
Alternatives
Use standard "Conventional Commits" tooling (e.g., commitlint): While powerful, they lack the specific strictness of our Subsystem/Ticket requirement and local-first integration preference.
Manual enforcement: Prone to human/agent error and drift.
Acceptance Criteria
commit-msg hook successfully blocks invalid commits and missing tickets.
generate_changelog.py produces a correct generic changelog from git history.
bump_version.py correctly identifies breaking changes vs. features vs. fixes.
Risks / Dependencies
Adoption: Agents/Developers must install the hooks locally. We need an install_hooks.py to simplify this.
Git History: Existing history might not be compliant. The tools should handle non-compliant legacy commits gracefully (e.g. ignore them or group under "Other").
Worklog
2026-01-07 07:25 [agent=antigravity] Created from template.
2026-01-07 16:40 [agent=antigravity] Populated Epic with detailed goals and scope based on KCC-STCC spec.
2026-01-07 20:05 [agent=antigravity] Expanded scope to include Backlog Quality Linter (Agent Discipline) per user review.
1---2name: 0000-dorgonman-kano-agent-backlog-s-53description: Context4---56# Context78Standardizing commit messages is critical for traceability and automation in multi-agent/multi-developer projects.9Currently, commit messages may vary in format, making it difficult to generate accurate changelogs or determine version bumps automatically.10The `kano-commit-convention-skill` provides a standard way to enforce the **KCC-STCC** (Subsystem + Type + Ticket) convention.1112# Goal1314Provide a drop-in skill that:151. **Enforces** commit conventions at the source (Git hooks).162. **Automates** release artifacts (Changelog, Versioning) based on commit history.173. **Educates** agents and developers on the KCC-STCC format.1819# Non-Goals2021- Replacing the version control system itself (supports Git, but methodology is VCS-agnostic).22- Enforcing workflows outside of commit message formatting (e.g., branching strategies).2324# Approach2526We will implement this skill via three main pillars:271. **Commit Linting**: A `commit-msg` hook and linter script to validate messages against the KCC-STCC regex, including ticket existence checks.282. **Changelog**: A generator script that parses valid commits and produces a grouped Markdown changelog.293. **Versioning**: A bumper script that suggests semantic version updates (Major/Minor/Patch) based on commit types.3031# Alternatives3233- Use standard "Conventional Commits" tooling (e.g., commitlint): While powerful, they lack the specific strictness of our Subsystem/Ticket requirement and local-first integration preference.34- Manual enforcement: Prone to human/agent error and drift.3536# Acceptance Criteria3738- [ ] `commit-msg` hook successfully blocks invalid commits and missing tickets.39- [ ] `generate_changelog.py` produces a correct generic changelog from git history.40- [ ] `bump_version.py` correctly identifies breaking changes vs. features vs. fixes.4142# Risks / Dependencies4344- **Adoption**: Agents/Developers must install the hooks locally. We need an `install_hooks.py` to simplify this.45- **Git History**: Existing history might not be compliant. The tools should handle non-compliant legacy commits gracefully (e.g. ignore them or group under "Other").4647# Worklog48492026-01-07 07:25 [agent=antigravity] Created from template.502026-01-07 16:40 [agent=antigravity] Populated Epic with detailed goals and scope based on KCC-STCC spec.512026-01-07 20:05 [agent=antigravity] Expanded scope to include Backlog Quality Linter (Agent Discipline) per user review.
Run npx skillmds@latest add majiayu000/0000-dorgonman-kano-agent-backlog-s-5 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Context It is listed under Product & Planning on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.
majiayu000