treeherder

Query Mozilla Treeherder CI job results, failure analysis, and test history via treeherder-cli or REST API.

3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jwmossmoz/agent-skills --skill treeherder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: treeherder
Source: https://github.com/jwmossmoz/agent-skills/tree/main/skills/treeherder
Command: npx skills add https://github.com/jwmossmoz/agent-skills --skill treeherder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires treeherder-client, requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Query Mozilla Treeherder for CI job results, failure analysis, and test history.

Core Features & Use Cases

  • Fetch failed jobs for a given revision
  • Group failures by test across platforms to spot cross-branch issues
  • Compare revisions and inspect similar history to identify regressions
  • Retrieve job logs and artifacts via Treeherder REST API when needed

Quick Start

Invoke treeherder-cli with a revision to fetch its failed jobs.

Frequently Asked Questions about treeherder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Mozilla Treeherder for CI job results by revision?

Query Mozilla Treeherder for CI job results by invoking treeherder-cli with a specific revision to fetch failed jobs. It uses the command-line interface as the primary method and falls back to the Treeherder REST API when needed.

How does failure analysis work when debugging across multiple branches?

Failure analysis works by grouping failures by test across platforms to spot cross-branch issues. It compares revisions and inspects similar history to identify regressions across Mozilla repositories.

Can I retrieve job logs and artifacts from the Treeherder REST API?

You can retrieve job logs and artifacts using the Treeherder REST API. It provides access to these resources as a fallback when the primary treeherder-cli interface is not sufficient for your needs.

Do I need the treeherder-client package to perform failure analysis?

You need the treeherder-client package and requests library to perform failure analysis. These dependencies enable the command-line interface used to query job results and test history.

What's the best way to spot cross-branch issues in CI test history?

The best way to spot cross-branch issues is to group failures by test across platforms. This allows you to compare revisions and inspect similar history to identify regressions across repositories.

Why does treeherder-cli fall back to the REST API for log access?

Treeherder-cli falls back to the REST API for log access when the command-line interface cannot retrieve specific job logs and artifacts. It ensures complete access to debugging data across repositories.