{
  "context": "This evaluation assesses how effectively the engineer uses cz-git's custom type management capabilities to implement a commit type configuration system. The focus is on proper usage of type configuration structures, validation patterns, and type management APIs.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Type Structure Definition",
      "description": "Uses cz-git's TypesOption structure with 'value', 'name', and optional 'emoji' fields to define custom commit types",
      "max_score": 20
    },
    {
      "name": "Types Append Configuration",
      "description": "Implements typesAppend functionality to merge custom types with default conventional commit types rather than replacing them entirely",
      "max_score": 25
    },
    {
      "name": "Type Validation Logic",
      "description": "Correctly extracts and validates commit types from messages in conventional commit format (type(scope): subject or type: subject) using type value matching",
      "max_score": 20
    },
    {
      "name": "Configuration Loading",
      "description": "Implements proper configuration loading that handles UserConfig-style objects with type-related options (types, typesAppend)",
      "max_score": 15
    },
    {
      "name": "Type Display Formatting",
      "description": "Formats type information for display including value, name, and emoji fields in a user-friendly way",
      "max_score": 10
    },
    {
      "name": "Default Types Handling",
      "description": "Correctly includes or references the standard conventional commit types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert)",
      "max_score": 10
    }
  ]
}