build-test-report

Build-test-report automates Maven build and test execution in a single atomic operation, returning JSON results with status, durations, and test outcomes. Run the script with `/workspace/main/.claude/scripts/build-test-report.sh` to execute both steps coordinated and receive programmatic output.

Yes. The script accepts flags like `--skip-tests` to compile only, `--profile` to select Maven profiles, and `--module` to target specific modules. Combine flags in one command: `build-test-report.sh --module formatter --profile dev --skip-tests`.

Atomic execution runs the full build and test cycle as a single coordinated step, ensuring consistency and eliminating partial states. This reduces round-trips between build and test phases, making it ideal for local pre-commit validation and CI-like checks without orchestrating separate commands.

Structured JSON output consolidates build and test results—including status, timing, and outcomes—into one machine-readable payload. This eliminates parsing unstructured logs, reduces LLM interaction overhead, and integrates easily with downstream reporting and automation tools.

You need Bash and a Maven wrapper available in your project. The script works with any Maven-based project structure and supports flags for customizing the build scope. No additional dependencies beyond the standard Maven toolchain are required.

Yes. Use `--module` to target specific modules and `--profile` to activate Maven profiles, allowing you to run partial builds and tests without executing the entire project suite. This is useful for focused verification during development.