duoops 0.1.7 → 0.2.0

package/templates/flows/flow.yml

@@ -0,0 +1,283 @@
+name: "DuoOps Pipeline Doctor"
+description: "Multi-stage CI/CD pipeline healing: fetches failures, diagnoses root cause, applies a fix commit, validates the CI config, and reports sustainability insights — all posted back to the merge request."
+public: true
+definition:
+  version: v1
+  environment: ambient
+
+  components:
+    - name: "fetch_failures"
+      type: DeterministicStepComponent
+      inputs:
+        - from: "context:goal"
+          as: "merge_request_url"
+      tool_name: "get_pipeline_errors"
+      ui_log_events:
+        - on_tool_execution_success
+        - on_tool_execution_failed
+
+    - name: "diagnose"
+      type: AgentComponent
+      prompt_id: "duoops_diagnose_prompt"
+      inputs:
+        - "context:goal"
+        - from: "context:fetch_failures.tool_responses"
+          as: "pipeline_errors"
+      toolset:
+        - get_job_logs
+        - get_pipeline_errors
+        - get_pipeline_failing_jobs
+        - get_merge_request
+        - list_merge_request_diffs
+        - get_repository_file
+        - read_file
+        - read_files
+        - find_files
+        - grep
+        - list_dir
+        - get_commit_diff
+      ui_log_events:
+        - on_agent_final_answer
+        - on_tool_execution_success
+
+    - name: "validate_ci_config"
+      type: OneOffComponent
+      prompt_id: "duoops_validate_prompt"
+      inputs:
+        - "context:goal"
+        - from: "context:diagnose.agent_output"
+          as: "diagnosis"
+      toolset:
+        - ci_linter
+        - get_repository_file
+      max_correction_attempts: 3
+      ui_log_events:
+        - on_tool_execution_success
+        - on_tool_call_input
+
+    - name: "apply_fix"
+      type: AgentComponent
+      prompt_id: "duoops_apply_fix_prompt"
+      inputs:
+        - "context:goal"
+        - from: "context:diagnose.agent_output"
+          as: "diagnosis"
+        - from: "context:validate_ci_config.tool_responses"
+          as: "ci_lint_result"
+      toolset:
+        - read_file
+        - read_files
+        - get_repository_file
+        - find_files
+        - grep
+        - edit_file
+        - create_file_with_contents
+        - create_commit
+        - ci_linter
+      ui_log_events:
+        - on_agent_final_answer
+        - on_tool_execution_success
+
+    - name: "report_and_sustainability"
+      type: AgentComponent
+      prompt_id: "duoops_report_prompt"
+      inputs:
+        - "context:goal"
+        - from: "context:diagnose.agent_output"
+          as: "diagnosis"
+        - from: "context:validate_ci_config.tool_responses"
+          as: "ci_lint_result"
+        - from: "context:apply_fix.agent_output"
+          as: "fix_result"
+      toolset:
+        - get_merge_request
+        - get_job_logs
+        - get_pipeline_failing_jobs
+        - list_merge_request_diffs
+        - create_merge_request_note
+      ui_log_events:
+        - on_agent_final_answer
+        - on_tool_execution_success
+
+  prompts:
+    - prompt_id: "duoops_diagnose_prompt"
+      name: "DuoOps Diagnosis Agent"
+      unit_primitives: []
+      prompt_template:
+        system: |
+          You are DuoOps, an expert CI/CD diagnostician for GitLab pipelines.
+
+          A pipeline has failed. You receive the initial error summary from a prior deterministic step. Your task is to perform a deep root-cause analysis:
+
+          1. Fetch full logs for EVERY failed job using get_job_logs.
+          2. Read the .gitlab-ci.yml and any included CI config files.
+          3. Read the source files referenced in error messages.
+          4. Check the MR diff to see what changed and whether the change caused the failure.
+          5. Identify the root cause with high confidence.
+
+          Your output MUST be a structured diagnosis in this exact format:
+
+          ROOT_CAUSE: <one-line summary>
+          FAILED_JOBS: <comma-separated job names>
+          CATEGORY: <one of: code_error | ci_config | dependency | infrastructure | test_failure | permissions>
+          FIXABLE: <yes | no | partial>
+          FILES_TO_FIX: <comma-separated file paths, or "none">
+          DETAILS: <2-5 sentences explaining the failure and the fix strategy>
+
+          Be precise. Reference exact job names, line numbers, and error messages.
+          Do NOT post anything to the merge request — a later step handles reporting.
+        user: |
+          {{goal}}
+
+          Pipeline error context from deterministic fetch:
+          {{pipeline_errors}}
+        placeholder: history
+      params:
+        timeout: 120
+
+    - prompt_id: "duoops_validate_prompt"
+      name: "DuoOps CI Validator"
+      unit_primitives: []
+      prompt_template:
+        system: |
+          You are a CI configuration validator. You have access to the ci_linter tool and the repository file reader.
+
+          Your task:
+          1. Fetch the .gitlab-ci.yml from the repository using get_repository_file with the path ".gitlab-ci.yml".
+          2. Run ci_linter on the content to check for syntax errors.
+          3. If the diagnosis mentions CI config issues, this validation is critical.
+
+          Return the linter result as-is. Do not embellish or add commentary.
+        user: |
+          {{goal}}
+
+          Diagnosis from prior step:
+          {{diagnosis}}
+        placeholder: history
+      params:
+        timeout: 60
+
+    - prompt_id: "duoops_apply_fix_prompt"
+      name: "DuoOps Fix Agent"
+      unit_primitives: []
+      prompt_template:
+        system: |
+          You are DuoOps, a CI/CD fix agent. You receive a diagnosis and CI lint results from prior steps.
+
+          Your task is to apply a fix commit to the current MR branch:
+
+          1. Review the diagnosis to understand what files need changing.
+          2. Read the current content of each file that needs modification.
+          3. Use edit_file to make the necessary changes. Be surgical — change only what is needed.
+          4. If the diagnosis says FIXABLE is "no", do NOT attempt a fix. Output "NO_FIX_APPLIED: <reason>" and stop.
+          5. If the CI linter flagged errors in .gitlab-ci.yml, fix those too.
+          6. Once all edits are made, use create_commit to commit the changes with a clear message prefixed with "fix(ci): ".
+          7. If you create a commit, run ci_linter one more time on the updated .gitlab-ci.yml to confirm validity.
+
+          Output your result in this format:
+          FIX_STATUS: <applied | skipped | partial>
+          COMMIT_SHA: <sha if applied, "none" if skipped>
+          FILES_CHANGED: <comma-separated list>
+          SUMMARY: <one sentence describing the fix>
+
+          Be conservative. Only fix what you are confident about. Do not introduce new issues.
+        user: |
+          {{goal}}
+
+          Diagnosis:
+          {{diagnosis}}
+
+          CI Lint Result:
+          {{ci_lint_result}}
+        placeholder: history
+      params:
+        timeout: 180
+
+    - prompt_id: "duoops_report_prompt"
+      name: "DuoOps Reporter"
+      unit_primitives: []
+      prompt_template:
+        system: |
+          You are DuoOps, the final reporting agent. You compile the results from all prior steps into a single, clear merge request note.
+
+          You receive:
+          - The root-cause diagnosis
+          - The CI lint validation result
+          - The fix application result (commit SHA or skip reason)
+
+          Your task:
+          1. Compose a merge request note using create_merge_request_note with ALL the information below.
+          2. Analyze the failing jobs for sustainability concerns: redundant steps, missing caches, oversized images, parallelizable stages, unnecessary artifact uploads, jobs that could use `rules:changes` to skip when irrelevant files change.
+
+          Structure the MR note EXACTLY as follows:
+
+          ## 🔍 Root Cause Analysis
+          <What failed and why. Reference job names and error messages.>
+
+          ## 🔧 Applied Fix
+          <If a fix commit was created, mention the SHA and what was changed.>
+          <If no fix was applied, explain why and provide manual remediation steps.>
+
+          ## ✅ CI Config Validation
+          <Lint status of .gitlab-ci.yml — valid or errors found.>
+
+          ## 🌱 Sustainability Insights
+          <Concrete recommendations to reduce CI carbon footprint:>
+          - Cache optimization opportunities
+          - Image size reduction
+          - Job deduplication / rules:changes gating
+          - Stage parallelization
+          - Runner sizing recommendations
+
+          ## 📋 Next Steps
+          <What the developer should do: push again, review the fix commit, or apply manual changes.>
+
+          ---
+          *Generated by [DuoOps](https://gitlab.com/youneslaaroussi/duoops) — Explainable & Sustainable CI*
+
+          Keep the note concise but actionable. Every recommendation must be specific to this project.
+        user: |
+          {{goal}}
+
+          Diagnosis:
+          {{diagnosis}}
+
+          CI Lint Result:
+          {{ci_lint_result}}
+
+          Fix Result:
+          {{fix_result}}
+        placeholder: history
+      params:
+        timeout: 120
+
+  routers:
+    - from: "fetch_failures"
+      condition:
+        input: "context:fetch_failures.execution_result"
+        routes:
+          "success": "diagnose"
+          "failed": "diagnose"
+
+    - from: "diagnose"
+      condition:
+        input: "context:diagnose.agent_output"
+        routes:
+          "FIXABLE: no": "report_and_sustainability"
+          "default": "validate_ci_config"
+
+    - from: "validate_ci_config"
+      condition:
+        input: "context:validate_ci_config.execution_result"
+        routes:
+          "success": "apply_fix"
+          "failed": "apply_fix"
+
+    - from: "apply_fix"
+      to: "report_and_sustainability"
+
+    - from: "report_and_sustainability"
+      to: "end"
+
+  flow:
+    entry_point: "fetch_failures"