opsx-apply-loop

Orchestrate iterative apply and verify cycles for app changes in Docker.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill opsx-apply-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-apply-loop
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/opsx-apply-loop
Command: npx skills add https://github.com/ConductionNL/decidesk --skill opsx-apply-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Iteratively applying changes, verifying outcomes, and archiving results across apps is tedious and error-prone. This skill orchestrates the entire loop inside an isolated Docker container, ensuring consistency and traceability.

Core Features & Use Cases

  • Autonomous orchestration of apply→verify→archive loops inside a Docker container per app change.
  • Optional host-side test cycles after verify, and automatic GitHub issue syncing and branch management for tracked changes.
  • Complete audit trail with per-run logs, iteration counts, and explicit success/failure states to support recovery and collaboration.

Quick Start

Run opsx-apply-loop for a specific app/change to start the autonomous apply–verify loop in Docker.

Frequently Asked Questions about opsx-apply-loop

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

FAQPage Schema
How do I automate apply and verify loops for app changes inside Docker?

Automating apply and verify loops in Docker involves orchestrating iterative cycles for app changes inside an isolated container. This process handles step-by-step tasks from applying changes to running verifications, automatically maintaining per-change feature branches and logging progress for audit and recovery.

Does this Docker workflow support automatic GitHub issue syncing and feature branch management?

Yes, the Docker workflow supports automatic GitHub issue syncing and branch management for tracked changes. It maintains per-change feature branches autonomously throughout the apply and verify cycles to ensure consistency and traceability across multiple apps.

What is the best way to run host-side tests after verifying app changes in a Docker container?

The best way to run host-side tests is to use the optional host-side test cycles after the verify step. This executes automatically within the orchestration loop, ensuring changes are validated both inside the Docker container and on the host before archiving on success.

Can I use autonomous DevOps workflows to archive successful app changes across multiple apps?

Yes, you can use autonomous DevOps workflows to archive successful app changes across multiple apps. The workflow archives on success after iterating through apply and verify cycles, providing a complete audit trail with per-run logs and explicit success or failure states.

How do predefined prompts work in autonomous Docker testing workflows?

Predefined prompts in autonomous Docker testing workflows implement autonomous operation by guiding the orchestration of iterative apply and verify cycles. This ensures consistent step-by-step execution for app changes without manual intervention, maintaining traceable logs for recovery.

Why do I need per-run logs and iteration counts for Docker container workflows?

You need per-run logs and iteration counts for Docker container workflows to support recovery and collaboration. They provide a complete audit trail with explicit success or failure states, ensuring traceability and enabling effective debugging of autonomous apply and verify loops.