{
  "context": "This criteria evaluates how effectively the engineer uses Lerna's exec command to execute shell commands across multiple packages in a monorepo, capture output, and process package-specific environment variables.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses lerna exec",
      "description": "The solution uses the 'lerna exec' command (either via CLI or programmatically) to execute commands across packages rather than manually iterating through package directories.",
      "max_score": 30
    },
    {
      "name": "Captures command output",
      "description": "The solution properly captures and processes the stdout output from the lerna exec command execution, enabling the extraction of line count data from each package.",
      "max_score": 20
    },
    {
      "name": "Accesses package context",
      "description": "The solution leverages Lerna's package-specific environment variables (such as LERNA_PACKAGE_NAME or similar mechanisms) to identify which package produced each output, or uses lerna list/programmatic APIs to map outputs to packages.",
      "max_score": 25
    },
    {
      "name": "Executes shell commands",
      "description": "The solution passes appropriate shell commands (like 'find . -name \"*.js\" | xargs wc -l' or similar) to lerna exec that will be executed in each package's directory context.",
      "max_score": 15
    },
    {
      "name": "Generates correct report",
      "description": "The solution correctly parses the command output and generates a JSON report with the required structure (packages array with packageName and lineCount fields), sorted alphabetically by package name.",
      "max_score": 10
    }
  ]
}