kano-commit-convention-skill
Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.
Best use case
kano-commit-convention-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.
Teams using kano-commit-convention-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/kano-commit-convention-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How kano-commit-convention-skill Compares
| Feature / Agent | kano-commit-convention-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Commit/change description convention (KCC) with Subsystem + Type + Ticket formatting, lint rules, and VCS-agnostic guidance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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)Related Skills
function-ordering-conventions
Defines the function ordering conventions, where functions that compose other functions appear earlier in the file, regardless of the file type.
commit
Create commits with code quality checks and conventional commit messages
banking-domain-conventions
Use when writing code in a Firefly Banking Platform (firefly-oss) service — applies domain organization, service taxonomy, inter-service communication patterns, POM inheritance, and platform-specific conventions
Action Pattern Conventions
This skill should be used when the user asks about "Laravel action pattern", "action class naming", "how to structure actions", "React component patterns", "Node.js service structure", "framework-specific conventions", or discusses creating reusable, focused classes following action pattern conventions in Laravel, Symfony, React, Vue, or Node.js projects.
kano-agent-backlog-skill
Local-first backlog workflow. Use when planning work, creating/updating backlog items, writing ADRs, enforcing Ready gate, generating views, or maintaining derived indexes (SQLite/FTS/embeddings).
git-commit-for-ai-agents
Commit changes to a git repository. Use whenever a git commit is to be executed.
entity-class-conventions
Sets the standards for entity class design including annotations, ID generation strategies, and relationship configurations for database interaction.
directory-naming-convention
Defines the directory naming convention.
adversarial-committee
Committee of personas with opposing propensities forcing genuine debate
push-commit
Stage all changes, commit with a descriptive message, and push to the remote. Trigger with "push commit", "commit and push", "push changes", "/push-commit".
git-create-commit-skill
Use when creating git commits - mandates commits format with required scopes for all new commits, provides scope discovery from codebase structure, and prevents rationalization under pressure (emergency, fatigue, ambiguity)
git-commit-push
This skill should be used when the user wants to commit their work to git and push to GitHub. It guides through reviewing changes, crafting meaningful commit messages following project conventions (including Conventional Commits when detected), creating commits with security checks, and pushing to remote repositories.