Skip to content

bestdeejay-design/agent-skills / skills/commit-lint

commit-lint

Verified

Validate git commit messages against Conventional Commits v1.0.0. Script commit_lint.py reads `git log` (subprocess) of one or more repositories (or stdin with --stdin), parses each commit into type/scope/subject, and reports violations: missing type, invalid type, type case, scope, subject length (default 50), subject capitalization, trailing dot/space, header length (100), body line length (72). Plain-text Markdown-friendly report or JSON (--json). Exit codes: 0 all clean, 1 violations found, 2 error. Pure Python 3 stdlib, offline, read-only. Closes the loop for commit-message-writer and version-bumper.

FileKindSize
SKILL.mdskill md8.4 KB
evals/evals.jsonconfig511 B
references/canonical-patterns.mdmarkdown5.7 KB
scripts/commit_lint.pyscript13.5 KB
skill.jsonconfig1.9 KB

skill.json

View on GitHub
{
  "name": "commit-lint",
  "version": "1.0.0",
  "description": "Validate git commit messages against Conventional Commits v1.0.0. Script commit_lint.py reads `git log` (subprocess) of a real repository (or stdin with --stdin), parses each commit as <type>(scope)!: subject, and reports violations: missing type, invalid type, type case, subject length (default 50), subject capitalization, trailing dot/space, header length (default 100), body line length (default 72). Plain-text Markdown report or JSON (--json). Exit codes: 0 all clean, 1 violations found, 2 error. Pure Python 3 stdlib, offline, read-only. Closes the loop for commit-message-writer and version-bumper. Triggers: 'commit lint', 'lint commits', 'conventional commits check', 'проверка коммитов', 'валидация коммитов', 'commit message check', 'check commit messages', 'conventional commit lint'.",
  "author": "best",
  "license": "MIT",
  "keywords": [
    "commit",
    "lint",
    "conventional-commits",
    "git",
    "validation",
    "commitlint",
    "gitlint",
    "commit message",
    "коммиты",
    "проверка"
  ],
  "triggers": [
    "commit lint",
    "lint commits",
    "commit message lint",
    "conventional commits",
    "conventional commit check",
    "check commit messages",
    "validate commits",
    "commit message validation",
    "проверка коммитов",
    "валидация коммитов",
    "проверь коммиты",
    "conventional commit lint",
    "commit style check",
    "commit-lint"
  ],
  "category": "code",
  "entrypoint": "SKILL.md",
  "files": [
    "SKILL.md",
    "skill.json",
    "scripts/commit_lint.py",
    "references/canonical-patterns.md",
    "evals/evals.json"
  ],
  "requirements": {
    "tools": [
      "python3"
    ],
    "script": "scripts/commit_lint.py",
    "permissions": [
      "file:read",
      "exec"
    ]
  },
  "updated": "2026-08-09"
}
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall