iterate

Run post-deploy incident response with regression tests and approval gates.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill iterate-luyzkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterate
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/iterate
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill iterate-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes reported bugs and hardens stable features after deploy by enforcing a regression-test-first workflow and a structured post-deploy iteration loop.

Core Features & Use Cases

  • Incident Response: Captures error context, proposes root-cause hypothesis, writes a regression test that must fail, then applies a minimal fix with approval and retries up to three times.
  • Defensive Hardening: Improves reliability and security in a focused, category-driven way (rate limiting, circuit breaker, timeout, fallback, and config centralization via a dedicated delegation).
  • Compound Decision Gate: After incident response and hardening, evaluates completed execution plans and captures durable lessons learned for reuse.

Quick Start

Run the iterate skill with an incident description like "incident: checkout fails with 500 and shows stack trace in logs" to drive regression-test creation, approved fix, and a final completion signal.

Frequently Asked Questions about iterate

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

FAQPage Schema
How do I automate incident response for production bugs?

Automate incident response by capturing error context, proposing a root-cause hypothesis, and writing a regression test that must fail before applying a minimal fix. The workflow retries fixes up to three times with required diff approval.

What is the best way to harden production features after deployment?

Defensive hardening improves reliability and security through category-driven actions like rate limiting, circuit breaker implementation, timeout management, fallback configuration, and config centralization within a structured post-deploy iteration loop.

How do I enforce regression testing before applying a production fix?

Enforce regression testing by requiring a test that explicitly fails against the current bug before applying any fix. A diff-before-apply safeguard and approval gate ensure only tested, minimal changes reach production.

Can I use this post-deploy workflow without setting up telemetry?

No, this workflow requires telemetry start and end signals to function properly. It uses deploy context, telemetry data, and provided logs to detect errors and drive the post-deploy iteration loop correctly.

How does a compound decision gate work for post-deploy hardening?

A compound decision gate evaluates completed execution plans after incident response and hardening phases. It captures durable lessons learned from the post-deploy process for future reuse, emitting a machine-readable completion signal.