iterate-fix

Triage build, deploy, and test failures with bounded retries and escalation.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/tonyandrewmeyer/cantrip --skill iterate-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate-fix
Source: https://github.com/tonyandrewmeyer/cantrip/tree/main/src/cantrip/skills/iterate-fix
Command: npx skills add https://github.com/tonyandrewmeyer/cantrip --skill iterate-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy-test-debug retry strategy introduces a formalised loop for the deploy → verify → test → fix cycle. Cantrip's autodeploy helpers already generate follow-up tasks after a failed BUILD, DEPLOY, or TEST run ( [Red/Green retry], [Acceptance fix], Diagnose deployment failure:, and [Watcher] tasks). This skill explains how to interpret that feedback, what to fix first, when to stop, and when to ask for help.

Core Features & Use Cases

  • Structured triage categorises failures into Environment, Deployment, Workload, and Test to guide prioritisation.
  • Bounded retries & escalation enforces a three-attempt budget and escalates when progress stalls.
  • Guided debugging workflow recommends interactive tools and steps to isolate root causes during follow-ups.

Quick Start

Start by identifying the failing BUILD/DEPLOY/TEST task and invoke the iterate-fix workflow to triage the failure and bound retries.

Frequently Asked Questions about iterate-fix

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

FAQPage Schema
How do I manage iterative build and deploy retries without getting stuck in an endless loop?

A structured deploy-debug retry strategy uses bounded budgets and escalation rules to prevent endless loops. It categorizes failures into Environment, Deployment, Workload, and Test groups, applying per-failure budgeting to decide what to fix first and when to ask for help.

What is the best way to triage failures during a deploy-debug cycle?

The best way to triage deploy-debug failures is to categorize them into Environment, Deployment, Workload, and Test groups. This structured triage guides prioritization so you know exactly what to fix first after a failed BUILD, DEPLOY, or TEST run.

How do I know when to stop retrying a failed deployment and escalate?

You should stop retrying a failed deployment and escalate when progress stalls. A structured retry strategy enforces a three-attempt budget for deployments, preventing endless loops by triggering escalation rules when the allowed retry limit is exhausted.

How does a structured workflow handle interactive debugging for failed tests?

Structured workflows handle interactive debugging by recommending specific tools and steps to isolate root causes during follow-up tasks. This guides you through the verify and fix phases after a failed TEST run, ensuring structured feedback before applying fixes.

Can I use this retry strategy for Juju charm deployments?

Yes, you can apply this retry strategy to Juju charm deployments. The workflow handles iterative build, deploy, and test cycles, managing failure feedback and bounded retries specifically for charm deployment and debugging workflows.