ci-cd-review

Collect the full error output, reproduce the failure locally, identify the root cause, and apply a minimal patch. Then verify with npm run lint and npm run build, and summarize findings, risks, and rollback steps before merging.

Reproduce the error with the exact command, diagnose the root cause with evidence, apply the smallest possible diff, and re-run npm run lint and npm run build. Finish with a smoke test of key flows to confirm the feature still works.

The primary tooling is PowerShell, Node.js with npm, and Git, with Python as an optional secondary tool. The underlying review procedure of reproduce, diagnose, patch, and verify applies to other stacks, but the acceptance commands are npm-based.

Disabling lint or tests hides the underlying problem rather than fixing it and can let defects reach production. This workflow requires explicit approval before weakening any check and always prefers a minimal, targeted patch.

A checklist approach depends on accurate input such as complete error logs and correct file paths, so it cannot guess missing context. It also avoids broad refactors, meaning deep architectural issues may need a separate dedicated effort.