spacelift:debug

Analyze failed Spacelift run logs to identify error causes.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill spacelift-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spacelift:debug
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/spacelift/skills/debug
Command: npx skills add https://github.com/fabn/claude-plugins --skill spacelift-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Users often cannot determine why a Spacelift run failed, lacking clear logs, phase information, and actionable remediation steps.

Core Features & Use Cases

  • Detect failed runs and identify the relevant stack and run identifier.
  • Retrieve run history, phase‑level logs, and resource changes using Spacelift MCP tools or CLI fallbacks.
  • Parse Terraform error messages, map them to the failing phase, and generate concrete fix suggestions.
  • Example: When a planning phase fails for the “production‑api” stack, the skill gathers the logs, isolates the error, and advises on missing permissions or configuration issues.

Quick Start

Ask the spacelift debug skill to investigate the failed run for stack “my-app‑prod”.

Frequently Asked Questions about spacelift:debug

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

FAQPage Schema
How do I debug a failed Spacelift run during the Terraform planning phase?

To debug a failed Spacelift run, you need the stack identifier and access to Spacelift MCP tools or CLI to retrieve phase-level logs. The tool isolates Terraform errors from the planning phase and generates concrete fix suggestions for configuration or permission issues.

Why does my Spacelift initialization phase fail and how can I get the logs?

Spacelift initialization failures can be diagnosed by retrieving run history and phase-level logs using Spacelift MCP tools or CLI fallbacks. Analyzing these logs pinpoints the exact initialization error and advises on missing permissions or configuration issues.

Can I analyze Spacelift run logs without the Spacelift MCP tools?

Yes, you can analyze Spacelift run logs using CLI fallbacks if Spacelift MCP tools are unavailable. You still need the relevant stack identifier and run identifier with permission to retrieve logs to map Terraform error messages to the failing phase.

What's the best way to troubleshoot Terraform errors in a Spacelift CI/CD pipeline?

The best way to troubleshoot Terraform errors in a Spacelift CI/CD pipeline is to gather run logs and resource changes, then parse the error messages to map them to the failing phase. This approach generates actionable remediation steps for the identified stack.

What information do I need to provide to investigate a failed Spacelift run?

To investigate a failed Spacelift run, you must provide the relevant stack identifier and have permission to retrieve run logs and changes. The skill uses this to detect failed runs and identify the specific run identifier for log analysis.

How do I get actionable fix tips for Spacelift stack failures?

To get actionable fix tips for Spacelift stack failures, retrieve the phase-level logs and resource changes for the failed run. The tool parses Terraform error messages, maps them to the failing phase, and generates concrete suggestions to resolve the issue.