Overview

This skill enforces the Kano commit format by linting commit messages and automating changelog updates. It serves as a lightweight OpenCode wrapper that points to canonical documentation, ensuring a single source of truth. It streamlines onboarding and release hygiene by maintaining a consistent history.

How This Skill Works

Run the provided lint command (python skills/kano-commit-convention-skill/scripts/kano-commit lint) to validate commits against the Kano format. The OpenCode adapter acts as a thin wrapper around canonical docs, guiding users and enabling automated changelog generation when commits pass lint.

When to Use It

• Enforce commit message standards across a team.
• Prepare releases and generate consistent changelog entries.
• Onboard new contributors who must follow the Kano format.
• Integrate into CI to fail on non-conforming commits.
• Audit project history for Kano-format compliance.

Quick Start

1. Step 1: Run the lint tool with: python skills/kano-commit-convention-skill/scripts/kano-commit lint
2. Step 2: Fix any failures according to Kano rules
3. Step 3: Commit using Kano-compliant messages and push to trigger automated changelog updates

Best Practices

• Run lint before merging to catch format issues.
• Configure CI to fail builds on lint violations.
• Document the Kano format guidelines in your repo.
• Use pre-commit hooks to check commits locally.
• Keep changelog entries aligned with the commit messages.

Example Use Cases

• A feature branch is linted during a PR and non-conforming commits are rejected.
• CI triggers a changelog update after a successful lint pass.
• Developers receive clear feedback on format violations via lint output.
• A release workflow generates standardized changelog entries from commits.
• New contributors learn Kano format from the lint script during onboarding.

Frequently Asked Questions