Build Code Review

Catch engineering issues that agents tend to miss when focused on feature implementation — the kind of problems that accumulate silently until a human reviewer points them out.

When to use

• After modifying build scripts or any file in the project's build directory
• After a PR that adds new build capabilities
• Periodically as a health check on build system complexity

Checklist

Scan the changed code (or the full build file if doing a health check) for these patterns. Any numeric values below are heuristics — the project should replace them with its own thresholds, tracked where it keeps project practice (e.g., AGENTS.md).

Async parallelization

• Are there sequential await calls where the operations have no data dependency on each other?
• Could any group of independent awaits be wrapped in Promise.all?