argus-build-diagnostics

# Argus Build Diagnostics

Use argus to analyze Xcode builds instead of parsing raw xcodebuild output.

## Installation

```bash
mise install github:tuist/argus@0.4.0
```

## Running a Build

Run xcodebuild with argus intercepting the build:

```bash
BUILD_TRACE_ID=$(uuidgen)
XCBBUILDSERVICE_PATH=$(which argus) BUILD_TRACE_ID=$BUILD_TRACE_ID xcodebuild build -scheme MyScheme
```

## Querying Build Results

After the build completes, use these commands to analyze results:

```bash
# Get build summary
argus trace summary --build $BUILD_TRACE_ID

# Get compilation errors
argus trace errors --build $BUILD_TRACE_ID

# Get slowest targets
argus trace slowest-targets --build $BUILD_TRACE_ID --limit 5

# Get build bottlenecks
argus trace bottlenecks --build $BUILD_TRACE_ID
```

## Dependency Analysis

Detect dependency issues in your project:

```bash
# Show what each target imports
argus trace imports --build $BUILD_TRACE_ID

# Find implicit dependencies (imports not declared as dependencies)
argus trace implicit-deps --build $BUILD_TRACE_ID

# Find redundant dependencies (declared but never imported)
argus trace redundant-deps --build $BUILD_TRACE_ID
```

Add `--json` flag for structured output.

## Dependency Graph and Linking Analysis

Query the build dependency graph with product type and linking information to identify optimization opportunities:

```bash
# Get the full dependency graph with linking info
argus trace graph --build $BUILD_TRACE_ID

# Query what a specific target depends on (transitive)
argus trace graph --source MyApp

# Query only direct dependencies
argus trace graph --source MyApp --direct

# Query what depends on a specific target
argus trace graph --sink CoreKit

# Find the path between two targets
argus trace graph --source MyApp --sink CoreKit

# Filter by dependency type
argus trace graph --source MyApp --label package
argus trace graph --source MyApp --label framework
```

### Available Labels

- `target`: Project targets
- `package`: Swift pac