How do I install the Kano Commit Convention Skill skill?

Run npx skillmds@latest add diegosouzapw/kano-commit-convention-skill 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.

Is Kano Commit Convention Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kano Commit Convention Skill?

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.

Is Kano Commit Convention Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kano Commit Convention Skill?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kano Commit Convention Skill by diegosouzapw

Name: Kano Commit Convention Skill
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

File contents

Kano Commit Convention (KCC)

Scope

This skill enforces a structured commit message convention (KCC-STCC) across the repository. It helps maintain a machine-readable history for automated changelogs and semantic versioning.

Use this skill when:

Setting up or troubleshooting commit message linting.
Generating release notes or identifying breaking changes.
Calculating the next semantic version.
Guidance on compliant commit subject formatting.

Non-negotiables

Format: [Subsystem][Type] Summary (Ticket)
Tickets: Always require an explicit ID (e.g., APP-123) or (NO-TICKET).
Breaking Changes: Must include [Breaking] in the subject or BREAKING CHANGE in the footer.
Backlog Sync: Linter verifies ticket existence against _kano/backlog/.

CLI (new, Typer)

Entrypoint: python skills/kano-commit-convention-skill/scripts/kano-commit <command>
Commands:
- lint message --message/--file [--json] [--language en|zh] [--strict-breaking]
- hook install|uninstall [--repo-root <path>]
- commit wizard
- release changelog|bump|release (changelog generation, version bump, release helper)
- doctor check (lightweight env check)

Legacy分散腳本已整合進 Typer CLI；請改用 kano-commit 子命令。

Configuration (kcc.json)

Customize KCCS behavior at the repo root:

{
  "allowed_types": ["Feature", "BugFix", "Refactor"],
  "language": "en"
}

language: en (default) or zh for localized linter messages.

Usage Examples

Installing Hooks

python scripts/vcs/install_hooks.py

Validating a Message Manually

python scripts/vcs/linter.py "my commit message"

Generating a P4 Changelog

python scripts/release/generate_changelog.py --vcs p4 --depot-path //depot/my-project/...

Performing a Release Dry-Run

python scripts/release/release.py --dry-run

Primary Reference

KCC Specification v0.0.1

---name: kano-commit-convention-skilldescription: Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.---# Kano Commit Convention (KCC)## ScopeThis skill enforces a structured commit message convention (KCC-STCC) across the repository. It helps maintain a machine-readable history for automated changelogs and semantic versioning.Use this skill when:- Setting up or troubleshooting commit message linting.- Generating release notes or identifying breaking changes.- Calculating the next semantic version.- Guidance on compliant commit subject formatting.## Non-negotiables- **Format**: `[Subsystem][Type] Summary (Ticket)`- **Tickets**: Always require an explicit ID (e.g., `APP-123`) or `(NO-TICKET)`.- **Breaking Changes**: Must include `[Breaking]` in the subject or `BREAKING CHANGE` in the footer.- **Backlog Sync**: Linter verifies ticket existence against `_kano/backlog/`.## CLI (new, Typer)- Entrypoint: `python skills/kano-commit-convention-skill/scripts/kano-commit <command>`- Commands: - `lint message --message/--file [--json] [--language en|zh] [--strict-breaking]` - `hook install|uninstall [--repo-root <path>]` - `commit wizard` - `release changelog|bump|release` (changelog generation, version bump, release helper) - `doctor check` (lightweight env check)Legacy分散腳本已整合進 Typer CLI；請改用 `kano-commit` 子命令。## Configuration (kcc.json)Customize KCCS behavior at the repo root:```json{ "allowed_types": ["Feature", "BugFix", "Refactor"], "language": "en"}```- `language`: `en` (default) or `zh` for localized linter messages.## Usage Examples### Installing Hooks```bashpython scripts/vcs/install_hooks.py```### Validating a Message Manually```bashpython scripts/vcs/linter.py "my commit message"```### Generating a P4 Changelog```bashpython scripts/release/generate_changelog.py --vcs p4 --depot-path //depot/my-project/...```### Performing a Release Dry-Run```bashpython scripts/release/release.py --dry-run```## Primary Reference- [KCC Specification v0.0.1](references/Kano-commit-convention.md)

Frequently asked questions

Kano Commit Convention Skill