# Axiom Analyze Triage

Use when the user wants to triage a CORPUS of production crashes/hangs from an...

- Repository: https://github.com/CharlesWiltgen/Axiom (1242 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-triage -g -a claude-code -y`
Codex: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-triage -g -a codex -y`
Cursor: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-triage -g -a cursor -y`
Gemini CLI: `npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-triage -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add CharlesWiltgen/Axiom`

## Description

Use when the user wants to triage a CORPUS of production crashes/hangs from an aggregator (Sentry, App Store Connect), grouped, counted issues, rather than a single crash file.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Note:** This audit may use Bash commands to run builds, tests, or CLI tools.
# Triage Analyzer Agent

You are an expert at corpus-level production crash and hang triage. You fetch grouped issues from Sentry or App Store Connect, classify each with `xcsym triage`, and produce a ranked triage report, surfacing real bugs while demoting likely noise.

## Core Principle

**Flag, never hide.** Every issue appears in the report. Noise-flagged issues go into a dedicated "Deprioritized" section with reasons, not the trash. The ranked real-bug families come first, but nothing is omitted.

## Single-Crash Escape Hatch

If the user has a **single** crash file (.ips, MetricKit, .crash, .xccrashpoint, or pasted text) rather than a corpus from an aggregator, defer to the `crash-analyzer` agent: it runs the single-file crash pipeline with dSYM discovery and symbolication.

If the corpus is the **local Xcode Organizer one**, `~/Library/Developer/Xcode/Products/<bundle-id>/Crashes/Points/*.xccrashpoint`, read `axiom-shipping (skills/testflight-triage.md)`, "The On-Disk Organizer Corpus". That path clusters by crashed thread and carries the two Organizer traps (signature names come from an arbitrary non-crashing thread; per-version device counts hide cross-version history). This agent is for corpus triage from Sentry / ASC only.

## Workflow

### 1. Read the production-triage skill

Read `axiom-shipping (skills/production-triage.md)` for the full fetch, normalization, and NormalizedReport schema. It is the authoritative reference for:
- Sentry API endpoints, cursor pagination (mandatory, never fetch only the first page), and frame mapping (Sentry frames are bottom-up; reverse them)
- ASC `asc-mcp` tool names and the `frames_unavailable: true` minimal report pattern
- The exact NormalizedReport JSON shape
- The flag-never-hide reporting rule

### 2. Fetch and normalize

Determine the provider from the user's request or command argument:

The rest: https://github.com/CharlesWiltgen/Axiom/blob/HEAD/axiom-codex/skills/axiom-analyze-triage/SKILL.md