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

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>

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>

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>

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>

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.