kano-commit-convention-skill

Lint commits against the Kano convention and generate changelogs.

1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/dorgonman/kano-agent-backlog-skill-demo --skill kano-commit-convention-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kano-commit-convention-skill
Source: https://github.com/dorgonman/kano-agent-backlog-skill-demo/tree/main/.goose/skills/kano-commit-convention-skill
Command: npx skills add https://github.com/dorgonman/kano-agent-backlog-skill-demo --skill kano-commit-convention-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill enforces the Kano commit format to improve traceability, change tracking, and historical readability of code changes, reducing ambiguous messages and manual changelog effort.

Core Features & Use Cases

  • Commit linting: Validate commits against the Kano convention to ensure consistent messages.
  • Changelog automation: Auto-generate changelog entries from lint results and commits.
  • Use Case: Integrate in CI pipelines to fail non-conforming commits and automatically update release notes.

Quick Start

  • Run lint: python skills/kano-commit-convention-skill/scripts/kano-commit lint
  • Run changelog: python skills/kano-commit-convention-skill/scripts/kano-commit changelog

Frequently Asked Questions about kano-commit-convention-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Kano-style commit messages in a CI pipeline?

You can enforce Kano-style commit messages by running the kano-commit lint script in your CI pipeline to validate commits and fail non-conforming changes automatically.

Can I automatically generate a changelog from Kano-format commits?

Yes, you can automatically generate a changelog by running the kano-commit changelog script, which creates release notes directly from your validated Kano-format commits.

What problem does standardizing commit messages with the Kano convention solve?

Standardizing commits with the Kano convention solves traceability and historical readability issues by reducing ambiguous messages and eliminating manual changelog effort in software development workflows.

Does commit linting for Kano-format require any specific environment setup?

Commit linting for Kano-format requires Python 3.10 or higher to execute the kano-commit script located under the scripts directory for linting and changelog generation.

When should I use an automated commit lint and changelog tool in software engineering?

You should use an automated commit lint and changelog tool when your software development workflow requires standardized commit messages, automated linting across CI pipelines, and auto-generated release notes for traceability.