Menu
Analyze CI logs from ci.aztec-labs.com. Use this instead of WebFetch for CI URLs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ci-logs |
| description | Analyze CI logs from ci.aztec-labs.com. Use this instead of WebFetch for CI URLs. |
| argument-hint | <url-or-hash> |
When you need to analyze logs from ci.aztec-labs.com, delegate to the analyze-logs subagent.
Extract the hash from the URL (e.g., http://ci.aztec-labs.com/e93bcfdc738dc2e0 → e93bcfdc738dc2e0)
Spawn the analyze-logs subagent using the Task tool with the hash and focus area (e.g. "errors", "test <name>", or a custom question) in the prompt.
User asks: "What failed in http://ci.aztec-labs.com/343c52b17688d2cd"
You do: Use the Task tool with subagent_type: "analyze-logs" and prompt including the hash 343c52b17688d2cd, focus on errors, and instruction to download with yarn ci dlog.
For specific test analysis: Same approach, but set the focus to the test name.
yarn ci dlogSpot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Reference for merge-train automation internals -- workflows, scripts, CI integration, and configuration. Use when modifying or debugging merge-train infrastructure.
Build and update the developer documentation site for a new release
Guide for working with merge-train branches -- creating PRs, choosing the right base branch, understanding labels, handling failures, and bypassing checks.
Create a well-formed Linear issue — with complete context for a fresh agent, a point estimate (1/2/3/5), and acceptance criteria. Works standalone or as part of planning a project with multiple issues. Use when asked to file/create/open a Linear issue, "make a ticket", or when breaking a plan into tracked work.
Build or adjust a Linear cycle — for a whole team or just yourself. Size capacity from last-3-cycle velocity, fill with backlog bugs/high-priority items first and project work after (in your chosen project focus order), with no unassigned issues. Use when planning/prepping a cycle for a team, or when one member wants to fill/rebalance their own cycle work.