fix-from-diagnostics

You can automatically fix compiler and linter errors by parsing diagnostic output and sharding the workload by package. This systematic approach prevents manual fixes from becoming time-consuming and error-prone in high-volume projects.

To resolve compiler errors from a diagnostics file, run the tool with your specific linter and target file path, such as `fix-from-diagnostics --tool tsc --from-file /path/to/project.ts`. This parses the output and applies fixes per package.

The best way to handle high volumes of linter errors is sharding the work by affected modules. Breaking down the errors into smaller packages allows for efficient resolution and includes optional adversarial review for large shards.

Yes, you can review automated linter fixes using the optional adversarial review feature. This is specifically designed for large shards, ensuring that automated error resolution maintains code quality before final integration.

This approach works with any compiler or linter that can output diagnostics to a file. You specify the tool, such as `tsc`, and provide the file path, allowing the system to parse the output and shard the fixing process by package.

You should avoid sharding compiler error fixes by package when a project has a very low error volume. In these cases, manually fixing each error is likely faster than setting up automated parsing and sharding workflows.