extract-errors

You can extract compilation errors and test failures from Gradle output by running an automated script that parses the build logs, structures the errors, and formats them as actionable items sorted by priority for quick resolution.

Yes, the error extraction process is compatible with both Android-only and Kotlin Multiplatform (KMP) projects, identifying compilation errors, coverage gaps, and test failures across these environments.

To get structured build errors from a specific module, you can target it directly in your command, such as specifying 'core:domain', and optionally include stack traces to gather deeper actionable insights for that module.

Automating the identification of coverage gaps in Android builds involves parsing Gradle output to automatically extract and structure test failures and compilation errors into prioritized, actionable items for developers.

Yes, you can include stack traces when parsing test failures from Gradle logs by using an inclusion flag during the extraction process, allowing you to capture deeper actionable insights alongside the prioritized error output.