{
  "context": "This criteria evaluates how effectively the engineer uses ESLint to implement Node.js-specific linting rules for detecting code quality issues. The focus is on proper usage of ESLint's API, configuration, and rule implementation.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "ESLint instantiation",
      "description": "Creates an ESLint instance using the ESLint class constructor (new ESLint()) or uses the Linter class for programmatic linting",
      "max_score": 20
    },
    {
      "name": "Rule configuration",
      "description": "Configures the three Node.js-specific rules: no-path-concat, no-process-exit, and no-sync using ESLint's configuration options (baseConfig or similar)",
      "max_score": 30
    },
    {
      "name": "File linting execution",
      "description": "Uses ESLint's lintFiles() method or Linter's verify()/verifyAndFix() methods to analyze the target file",
      "max_score": 20
    },
    {
      "name": "Results processing",
      "description": "Correctly extracts and processes linting results, accessing properties like messages, line numbers, and ruleId from ESLint's result format",
      "max_score": 20
    },
    {
      "name": "Rule-specific filtering",
      "description": "Filters or identifies messages specifically related to no-path-concat, no-process-exit, and no-sync rules from the ESLint results",
      "max_score": 10
    }
  ]
}