What is the problem?
用项目视角判断 ESLint error 修复任务能不能接：看规则名、影响范围、团队配置、CI 门禁、验证命令和交付边界，先诊断再修改。
Quick solution
Treat this as a Upwork case-study issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.
Read the deep guideDetailed steps
- Confirm the scenario, tool version, account permissions, inputs, and expected output before changing anything.
- Check configuration, logs, command output, and human review boundaries against the linked deep guide.
- Record the before and after result, then verify that the fix did not introduce platform, privacy, or delivery risk.
Commands or code
任务：ESLint 报错诊断
规则名：
影响文件：
原因判断：
修复方式：
是否禁用规则：
验证命令：
验证结果：
客户待确认：Risk notes
Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.