commit-validator — community commit-validator, agent-studio, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0

このスキルについて

Conventional Commits の仕様に対する自動コミットメッセージ検証が必要なコードレビューエージェントに最適です。 Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.

oimiragieo oimiragieo
[16]
[0]
Updated: 3/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 9/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
9/11
Quality Score
50
Canonical Locale
en
Detected Body Locale
en

Conventional Commits の仕様に対する自動コミットメッセージ検証が必要なコードレビューエージェントに最適です。 Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.

このスキルを使用する理由

Conventional Commits を使用して標準化されたコミットメッセージを適用するエージェントの能力を与え、pre-commit hooks および CI/CD パイプラインとシームレスに統合し、commitlint を使用して検証します。

おすすめ

Conventional Commits の仕様に対する自動コミットメッセージ検証が必要なコードレビューエージェントに最適です。

実現可能なユースケース for commit-validator

コードレビュー中に Conventional Commits 仕様に従ったコミットメッセージを検証する
pre-commit hooks でコミットメッセージの検証を自動化して一貫性を確保する
CI/CD パイプラインにコミット検証を統合してコード品質を向上させる

! セキュリティと制限

  • pre-commit hooks または CI/CD パイプラインと統合する必要がある
  • Conventional Commits 仕様に限定される
  • 検証のためにコミットメッセージにアクセスする必要がある

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is commit-validator?

Conventional Commits の仕様に対する自動コミットメッセージ検証が必要なコードレビューエージェントに最適です。 Validates commit messages against Conventional Commits specification using programmatic validation. Replaces the git-conventional-commit-messages text file with a tool that provides instant feedback.

How do I install commit-validator?

Run the command: npx killer-skills add oimiragieo/agent-studio/commit-validator. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for commit-validator?

Key use cases include: コードレビュー中に Conventional Commits 仕様に従ったコミットメッセージを検証する, pre-commit hooks でコミットメッセージの検証を自動化して一貫性を確保する, CI/CD パイプラインにコミット検証を統合してコード品質を向上させる.

Which IDEs are compatible with commit-validator?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for commit-validator?

pre-commit hooks または CI/CD パイプラインと統合する必要がある. Conventional Commits 仕様に限定される. 検証のためにコミットメッセージにアクセスする必要がある.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add oimiragieo/agent-studio/commit-validator. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use commit-validator immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

commit-validator

Install commit-validator, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

References (archive): SCAFFOLD_SKILLS_ARCHIVE_MAP.md — commit validation logic inspired by claude-flow v3 git-commit hook, everything-claude-code commitlint.

<identity> Commit Message Validator - Programmatically validates commit messages against the [Conventional Commits](https://www.conventionalcommits.org/) specification. </identity> <capabilities> - Before committing code - In pre-commit hooks - In CI/CD pipelines - During code review - To enforce team standards </capabilities> <instructions> <execution_process>

Step 1: Validate Commit Message

Validate a commit message string against Conventional Commits format:

Format: <type>(<scope>): <subject>

Types:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Code style changes (formatting, etc.)
  • refactor: Code refactoring
  • perf: Performance improvements
  • test: Adding or updating tests
  • chore: Maintenance tasks
  • ci: CI/CD changes
  • build: Build system changes
  • revert: Reverting a previous commit

Validation Rules:

  1. Must start with type (required)
  2. Scope is optional (in parentheses)
  3. Subject is required (after colon and space)
  4. Use imperative, present tense ("add" not "added")
  5. Don't capitalize first letter
  6. No period at end
  7. Can include body and footer (separated by blank line) </execution_process> </instructions>
<examples> <code_example> **Implementation**

Use this regex pattern for validation:

javascript
1const CONVENTIONAL_COMMIT_REGEX = 2 /^(feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert)(\(.+\))?: .{1,72}/; 3 4function validateCommitMessage(message) { 5 const lines = message.trim().split('\n'); 6 const header = lines[0]; 7 8 // Check format 9 if (!CONVENTIONAL_COMMIT_REGEX.test(header)) { 10 return { 11 valid: false, 12 error: 'Commit message does not follow Conventional Commits format', 13 }; 14 } 15 16 // Check length 17 if (header.length > 72) { 18 return { 19 valid: false, 20 error: 'Commit header exceeds 72 characters', 21 }; 22 } 23 24 return { valid: true }; 25}

</code_example>

<code_example> Valid Examples:

feat(auth): add OAuth2 login support
fix(api): resolve timeout issue in user endpoint
docs(readme): update installation instructions
refactor(components): extract common button logic
test(utils): add unit tests for date formatting

</code_example>

<code_example> Invalid Examples:

Added new feature  # Missing type
feat:new feature   # Missing space after colon
FEAT: Add feature  # Type should be lowercase
feat: Added feature  # Should use imperative tense

</code_example>

<code_example> Pre-commit Hook (.git/hooks/pre-commit):

bash
1#!/bin/bash 2commit_msg=$(git log -1 --pretty=%B) 3if ! node .claude/tools/validate-commit.mjs "$commit_msg"; then 4 echo "Commit message validation failed" 5 exit 1 6fi

</code_example>

<code_example> CI/CD Integration:

yaml
1# .github/workflows/validate-commits.yml 2- name: Validate commit messages 3 run: | 4 git log origin/main..HEAD --pretty=%B | while read msg; do 5 node .claude/tools/validate-commit.mjs "$msg" || exit 1 6 done

</code_example> </examples>

<examples> <formatting_example> **Output Format**

Returns structured validation result:

json
1{ 2 "valid": true, 3 "type": "feat", 4 "scope": "auth", 5 "subject": "add OAuth2 login support", 6 "warnings": [] 7}

Or for invalid messages:

json
1{ 2 "valid": false, 3 "error": "Commit message does not follow Conventional Commits format", 4 "suggestions": [ 5 "Use format: <type>(<scope>): <subject>", 6 "Valid types: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert" 7 ] 8}

</formatting_example> </examples>

<examples> <usage_example> **Example Commands**:
bash
1# Validate a commit message 2node .claude/tools/validate-commit.mjs "feat(auth): implement jwt login" 3 4# Validate from stdin (e.g. in a hook) 5echo "fix: incorrect variable name" | node .claude/tools/validate-commit.mjs

</usage_example> </examples>

<instructions> <best_practices> 1. **Validate Early**: Check commit messages before pushing 2. **Provide Feedback**: Show clear error messages with suggestions 3. **Enforce in CI**: Add validation to CI/CD pipelines 4. **Team Training**: Educate team on Conventional Commits format 5. **Tool Integration**: Integrate with Git hooks and IDEs </best_practices> </instructions>

Memory Protocol (MANDATORY)

Before starting: Read .claude/context/memory/learnings.md

After completing:

  • New pattern -> .claude/context/memory/learnings.md
  • Issue found -> .claude/context/memory/issues.md
  • Decision made -> .claude/context/memory/decisions.md

ASSUME INTERRUPTION: If it's not in memory, it didn't happen.

関連スキル

Looking for an alternative to commit-validator or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

149.6k
0
AI

flags

Logo of vercel
vercel

React フレームワーク

138.4k
0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク(強力なGPUアクセラレーション)

98.6k
0
開発者