CtrlK
BlogDocsLog inGet started
Tessl Logo

openkata/commit-conventions

Enforces Conventional Commits format and branch naming conventions, validating commit message structure (type/scope/description header), suggesting branch name patterns (feature/*, fix/*, hotfix/*), and enforcing breaking change notation. Use when the user is about to commit, creating a branch, reviewing commit history, preparing a pull request, setting up commit linting, or asking about commit message format, branch naming, or Conventional Commits.

97

1.03x
Quality

97%

Does it follow best practices?

Impact

97%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

branch-naming.mdreferences/

Branch Naming

Format

type/short-description
type/issue-number-short-description

Types

feature/, fix/, refactor/, docs/, test/, chore/, hotfix/

Rules

  • Lowercase, kebab-case (hyphens, not underscores)
  • 2-5 words, short but descriptive
  • Include issue number when applicable: fix/123-memory-leak
  • Create from main, delete after merge

Examples

feature/payment-integration
fix/789-session-timeout
refactor/api-error-handling
docs/setup-instructions
chore/upgrade-dependencies
hotfix/security-vulnerability

RATIONALE.md

SKILL.md

tile.json