ci-logs

Analyze CI logs from ci.aztec-labs.com to identify failures and errors.

449|615|Updated Feb 20, 2023

Search Tags:#automation #debugging #error analysis #analyze #log hash #CI logs

Ready to run

npx skills add https://github.com/AztecProtocol/aztec-packages --skill ci-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-logs
Source: https://github.com/AztecProtocol/aztec-packages/tree/main/.claude/skills/ci-logs
Command: npx skills add https://github.com/AztecProtocol/aztec-packages --skill ci-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes CI logs from ci.aztec-labs.com to identify failures and errors, enabling faster debugging without manual log digging.

Core Features & Use Cases

CI log analysis: Extracts error messages, stack traces, and failure patterns from logs.
Hash/URL support: Accepts a log hash or direct URL to the log resource for flexible access.
Rapid debugging: Produces concise summaries and actionable hints for developers.

Quick Start

Use the ci-logs skill to analyze a CI log by providing the log URL or hash. For example, paste the URL http://ci.aztec-labs.com/e93bcfdc738dc2e0 or the hash e93bcfdc738dc2e0 to spawn the analyze-logs agent with a prompt focused on errors.

Frequently Asked Questions about ci-logs

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

FAQPage Schema

How do I analyze CI logs when authentication blocks web fetching?▼

To analyze CI logs restricted by authentication, you can provide a direct log hash or URL from ci.aztec-labs.com. This bypasses access limitations by spawning an agent that focuses on extracting error messages and failure patterns for rapid debugging.

Can I use a log hash instead of a full URL for CI log analysis?▼

Yes, you can use a log hash instead of a full URL for CI log analysis. The tool accepts both direct URLs and hashes, such as 'e93bcfdc738dc2e0', to identify the log resource and extract stack traces and failure patterns.

What is the best way to debug CI pipeline failures quickly?▼

The best way to debug CI pipeline failures quickly is to analyze the logs for error messages and stack traces. Providing the CI log URL or hash generates concise summaries and actionable hints, eliminating the need for manual log digging.

Does the CI log analysis tool work with pipelines from ci.aztec-labs.com?▼

Yes, the CI log analysis tool specifically works with pipelines from ci.aztec-labs.com. It processes log hashes or URLs from this domain to identify failures, extract errors, and produce actionable debugging summaries.

Why should I use a log hash for error analysis instead of fetching directly?▼

You should use a log hash for error analysis when authentication or access restrictions prevent direct web fetching. Providing the hash allows the analysis agent to locate the specific CI log and extract failure patterns without encountering access barriers.