CtrlK
BlogDocsLog inGet started
Tessl Logo

git-commit-messages

Write clear, conventional commit messages that explain the why behind changes.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./git-commit-messages/SKILL.md
SKILL.md
Quality
Evals
Security

Git Commit Messages

Format

Follow Conventional Commits:

<type>(<scope>): <description>

[optional body]

Types

  • feat — new feature
  • fix — bug fix
  • refactor — restructuring without behavior change
  • chore — maintenance, deps, CI
  • docs — documentation only
  • test — adding or fixing tests

Guidelines

  1. Subject line — imperative mood, under 72 characters, no period
  2. Body — explain why, not what (the diff shows what)
  3. Scope — use the module or area affected (e.g. auth, api, db)
  4. Breaking changes — add BREAKING CHANGE: footer

Examples

Good

feat(notifications): add email templates for eval run results

Users need visibility into eval outcomes without checking the dashboard.
Three templates cover success, partial failure, and pipeline failure.

Bad

updated stuff
Repository
neil-tessl/nh-code-review-skills
Path

git-commit-messages/SKILL.md

Commit

240b3aa

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill