Skip to content
Back to skills

Kano Commit Convention Skill

ASecurity

Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.

  • 57 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 31, 2026
documentationpythongobash

Works with

  • cli

Security analysis

A100/100

Scanned May 31, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill kano-commit-convention-skill --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Kano Commit Convention Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Kano Commit Convention Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-kano-commit-convention-skill/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-kano-commit-convention-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: kano-commit-convention-skill
description: Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.
metadata:
  short-description: Commit message convention (KCC)
---

# 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:
```json
{
  "allowed_types": ["Feature", "BugFix", "Refactor"],
  "language": "en"
}
```
- `language`: `en` (default) or `zh` for localized linter messages.

## Usage Examples

### Installing Hooks
```bash
python scripts/vcs/install_hooks.py
```

### Validating a Message Manually
```bash
python scripts/vcs/linter.py "my commit message"
```

### Generating a P4 Changelog
```bash
python scripts/release/generate_changelog.py --vcs p4 --depot-path //depot/my-project/...
```

### Performing a Release Dry-Run
```bash
python scripts/release/release.py --dry-run
```

## Primary Reference
- [KCC Specification v0.0.1](references/Kano-commit-convention.md)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.