--- name: build-runner allowed-tools: Bash, Read, Glob description: >- Execute build/test commands and return structured summaries. Use for Maven, Node, or Python builds during dependency remediation. Use when the user says "build", "compile", "test", "verify", "run tests", "maven verify", "unit tests", or "build summary". Not for: deployment, CI/CD pipeline management, or code generation. --- # Build Runner Execute build commands and return concise summaries to preserve main agent context during dependency remediation. ## Purpose When running builds, the output can be 5,000+ lines. This skill: 1. Executes the appropriate build command 2. Captures all output internally 3. Parses for key information 4. Returns only a structured summary (~10 lines) This preserves the main agent's context for decision-making across multiple build cycles. The `@osdu` agent spawns build-runner as a sub-agent for exactly this reason. ## Path Resolution Projects are found in the OSDU workspace: - `$OSDU_WORKSPACE//` (regular clone) - `$OSDU_WORKSPACE//master/` (worktree clone) - Default: current working directory if OSDU_WORKSPACE is not set The `javatest.py` script is part of this plugin at `skills/maven/scripts/javatest.py`. ## Pre-Flight Checks ### 1. Find the project Check if the service exists in the workspace: ```bash OSDU_WORKSPACE="${OSDU_WORKSPACE:-$(pwd)}" ls "$OSDU_WORKSPACE//pom.xml" 2>/dev/null || \ ls "$OSDU_WORKSPACE//master/pom.xml" 2>/dev/null ``` If the project is not found, **use the `clone` skill to clone it first**, then continue with the build. ### 2. Check build tools ```bash java --version 2>/dev/null && mvn --version 2>/dev/null ``` If build tools are missing, **stop and use the `setup` skill** to install them. ## Supported Build Systems | System | Detection | Preferred Tool | Fallback | |--------|-----------|---------------|----------| | Maven (OSDU) | `pom.xml` + OSDU structure | `javatest.py` | `mvn` directly | | Maven (generic) | `pom.xml` | — | `mvn compile/test/verify` | | Node | `package.json` | — | `npm test`, `npm run build` | | Python | `pyproject.toml` | — | `pytest`, `pip install` | ## Execution ### For OSDU Maven Projects (Preferred) Use the `javatest.py` script for reliable, cross-platform execution with automatic profile handling. ```bash # Use the javatest.py script from the maven skill uv run skills/maven/scripts/javatest.py --project --validate # Compile only uv run skills/maven/scripts/javatest.py --project --compile # Run tests uv run skills/maven/scripts/javatest.py --project --test # Package uv run skills/maven/scripts/javatest.py --project --package ``` **If script not found:** Fall back to generic Maven commands (see below). **Key features:** - `--validate` automatically detects shared modules and builds with ALL profiles - Cross-platform (Windows, Linux, macOS) - Automatic service discovery - Structured error handling **When to use `--validate`:** - After modifying shared modules (names containing: core, common, shared, api, model) - When request mentions "shared module" or "all profiles" - For pre-commit validation of dependency changes ### Worktree Build Fix When building in a bare clone + worktree layout, the `git-commit-id` Maven plugin fails because it can't find `.git/`. **Always add this flag for worktree builds:** ```bash -Dmaven.gitcommitid.skip=true ``` Detect worktree layout by checking if `.git` is a file (not a directory): ```bash # If .git is a file → worktree layout → skip git-commit-id [ -f .git ] && GIT_SKIP="-Dmaven.gitcommitid.skip=true" || GIT_SKIP="" ``` ### For Generic Maven Projects ```bash # Compile only cd && mvn compile -q $GIT_SKIP 2>&1 # Compile + unit tests cd && mvn test -q $GIT_SKIP 2>&1 # Full build with all tests cd && mvn verify -q $GIT_SKIP 2>&1 ``` ### For Node Projects ```bash cd && npm test 2>&1 cd && npm run build 2>&1 ``` ### For Python Projects ```bash cd && pytest 2>&1 cd && pip install -e . 2>&1 ``` ## Response Format ALWAYS respond with this exact structure: ``` Build: Command: Status: PASSED | FAILED Duration: