delivery-rescue

Diagnoses CI failures, bug reports, and environment inconsistencies from logs, diffs, and contracts.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill delivery-rescue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-rescue
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/delivery-rescue
Command: npx skills add https://github.com/aurora-atoms/lattice --skill delivery-rescue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves delivery blockers by providing a structured, evidence-based diagnostic framework for CI failures, environment issues, and contract-breaking changes.

Core Features & Use Cases

  • Atomic Diagnosis: Provides specialized paths for CI red-to-green, bug reproduction, environment health, and contract validation.
  • Evidence-Grounded Assessment: Ensures all findings are backed by logs, diffs, and environment facts rather than speculation.
  • Use Case: When a CI pipeline fails unexpectedly, use this Skill to ingest the relevant logs and diffs to receive a ranked root-cause assessment and a verified next step for repair.

Quick Start

Use the delivery-rescue skill to diagnose the current CI failure by providing the relevant logs and the associated Feature Delivery Case context.

Frequently Asked Questions about delivery-rescue

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

FAQPage Schema
How do I diagnose unexpected CI pipeline failures using logs and diffs?

Diagnose CI pipeline failures by ingesting relevant logs and diffs to receive a ranked root-cause assessment. This provides a verified next step for repair based on verifiable evidence rather than speculation.

What is evidence-based diagnosis for software delivery blockers?

Evidence-based diagnosis resolves delivery blockers by analyzing logs, diffs, and contract definitions within a Feature Delivery Case. It enforces strict separation of facts from inferences to maintain delivery integrity.

How do I troubleshoot environment inconsistencies and bug reports without guessing?

Troubleshoot environment inconsistencies and bug reports through specialized diagnostic paths for environment health and bug reproduction. This grounds all findings in environment facts and verifiable evidence.

Can I validate contract-breaking changes within my feature delivery workflow?

Yes, validate contract-breaking changes by analyzing contract definitions alongside your Feature Delivery Case context. This ensures all assessments remain grounded in atomic capability selection and verifiable evidence.

When should I use an atomic diagnosis framework for CI red-to-green repair?

Use atomic diagnosis when a CI pipeline fails unexpectedly and you need a structured framework. It provides specialized paths for CI red-to-green repair, requiring logs and associated delivery case context.

Why does my root-cause assessment lack delivery integrity during troubleshooting?

Root-cause assessment lacks integrity when findings are not backed by verifiable evidence. Enforcing strict separation of facts from inferences ensures all diagnoses are grounded in logs and environment facts.