Autonomous CI Build Failure Triaging and Patch Pipeline Framework

Role: Principal Site Reliability Engineer specializing in autonomous DevSecOps and self-healing pipelines.

Context

• Repository Architecture: {{repo_architecture}}
• Continuous Integration Pipeline: {{ci_pipeline_type}}
• Build & Telemetry Ingestion Source: {{failure_telemetry_source}}
• Automated Patch Verification Policy: {{patch_verification_policy}}
• Sandboxed Execution Runtime: {{sandbox_runtime_environment}}
• Human-in-the-Loop Escalation Route: {{escalation_channel}}

Task

Design an end-to-end multi-agent workflow chaining framework that ingests build failures from {{failure_telemetry_source}}, isolates root-cause code diffs in {{repo_architecture}}, validates isolated candidate patches within {{sandbox_runtime_environment}}, and enforces {{patch_verification_policy}} before routing to {{escalation_channel}}.

Method

1. Map telemetry payload ingest handlers to parse logs, stack traces, and deterministic test exit codes.
2. Define the triage agent stage to pinpoint the exact commit range and blast radius across {{repo_architecture}}.
3. Formulate the code diagnosis agent state machine to extract failing abstract syntax trees and contextual source files.
4. Construct the code generation agent prompts and tool definitions for producing minimal, non-breaking candidate patches.
5. Specify the sandboxed validation stage to replay failed assertions against {{sandbox_runtime_environment}} and {{ci_pipeline_type}}.
6. Formulate fallback and rollback logic for patches that fail validation or introduce secondary regressions.
7. Establish the gatekeeping protocol enforcing {{patch_verification_policy}} and formatting the artifact for {{escalation_channel}}.

Constraints

• MUST include explicit state-transition diagrams and memory-passing structures between each agent stage.
• MUST NOT permit unverified code patches to merge without deterministic sandbox execution.
• Agent actions MUST maintain an idempotent audit trail of git operations and validation results.
• Scope every agent tool invocation strictly to the files modified within the culprit pull request or commit.
• All state transitions must define deterministic timeout and failure handling thresholds.

Output format

1. System Topology & Agent State Graph (listing inputs, state payloads, and outputs per node)
2. Agent Step-by-Step Chaining Specification (table with Node Name, Agent Role, Tools, Failure Policy)
3. Sandbox Execution & Verification Protocol (exact verification script flow and regression guardrails)
4. Pull Request & Escalation Payload Specification (markdown template for developer notification)

Self-review

• Confirm every variable from {{repo_architecture}} to {{escalation_channel}} is integrated into the workflow logic.
• Verify that deterministic recovery steps exist for hallucinated or failing patches.
• Ensure all agent tool boundaries adhere to the sandbox execution limits.