openshift · openshift-merge-bot · Mar 18, 2026 · Mar 15, 2026 · Mar 15, 2026 · Mar 15, 2026
diff --git a/.claude/commands/analyze-ci-for-release-manager.md b/.claude/commands/analyze-ci-for-release-manager.md
@@ -0,0 +1,223 @@
+---
+name: Analyze CI for Release Manager
+argument-hint: <release1,release2,...>
+description: Analyze CI for multiple MicroShift releases and produce an HTML summary
+allowed-tools: Skill, Bash, Read, Write, Glob, Grep, Agent
+---
+
+# analyze-ci-for-release-manager
+
+## Synopsis
+```
+/analyze-ci-for-release-manager <release1,release2,...>
+```
+
+## Description
+Accepts a comma-separated list of MicroShift release versions, runs the `analyze-ci-for-release` skill for each release, and produces a single HTML summary file consolidating all per-release results.
+
+## Arguments
+- `$ARGUMENTS` (required): Comma-separated list of release versions (e.g., `4.19,4.20,4.21,4.22`)
+
+## Implementation Steps
+
+### Step 1: Parse and Validate Arguments
+
+**Actions**:
+1. Split `$ARGUMENTS` by comma to get a list of release versions
+2. Trim whitespace from each version
+3. Validate that at least one release version is provided
+4. If no arguments provided, show usage and stop
+
+**Error Handling**:
+- If `$ARGUMENTS` is empty, display: "Usage: /analyze-ci-for-release-manager <release1,release2,...>" and stop
+
+### Step 2: Analyze Each Release
+
+**Actions**:
+1. For each release version from the parsed list, invoke the `analyze-ci-for-release` skill:
+   ```
+   Skill: analyze-ci-for-release, args: "<version>"
+   ```
+2. Run releases **sequentially** (each skill invocation is a full analysis)
+3. After each skill completes, note the summary report file path it produced (typically `/tmp/analyze-ci-release-<version>-summary.*.txt`)
+4. Track which releases succeeded and which failed
+
+**Progress Reporting**:
+```
+Analyzing release X/Y: <version>
+```
+
+### Step 3: Collect Per-Release Results
+
+**Actions**:
+1. After all releases are analyzed, gather all summary files:
+   - Look for `/tmp/analyze-ci-release-<version>-summary.*.txt` for each version
+   - Also look for per-job files: `/tmp/analyze-ci-release-<version>-job-*.txt`
+2. Read each summary file to extract the analysis content
+3. If a summary file is missing for a release, note it as "Analysis failed or produced no output"
+
+### Step 4: Generate HTML Summary Report
+
+**Goal**: Create a single HTML file at `/tmp/microshift-ci-release-manager-<timestamp>.html` that consolidates all per-release analyses.
+
+**Actions**:
+1. Generate the HTML report with the structure described below
+2. Save to `/tmp/microshift-ci-release-manager-<timestamp>.html` where `<timestamp>` is `YYYYMMDD-HHMMSS`
+3. **IMPORTANT**: Use the `Bash` tool with `cat <<'HTMLEOF' > /tmp/microshift-ci-release-manager-<timestamp>.html` (heredoc) to write the file, NOT the `Write` tool. This ensures the absolute `/tmp` path is used and avoids permission prompts.
+4. Display the file path to the user in the end.
+
+**HTML Structure**:
+
+The HTML file must be a self-contained, single-file document with embedded CSS. Use the following structure:
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <title>MicroShift CI Release Manager Report - YYYY-MM-DD</title>
+    <style>
+        /* Clean, professional styling */
+        body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; margin: 0; padding: 20px; background: #f5f5f5; color: #333; }
+        .container { max-width: 1200px; margin: 0 auto; }
+        h1 { color: #1a1a2e; border-bottom: 3px solid #e94560; padding-bottom: 10px; }
+        .release-section { background: white; border-radius: 8px; padding: 20px; margin: 20px 0; box-shadow: 0 2px 4px rgba(0,0,0,0.1); }
+        .release-header { display: flex; justify-content: space-between; align-items: center; }
+        .release-header h2 { color: #16213e; margin: 0; }
+        .badge { padding: 4px 12px; border-radius: 12px; font-size: 0.85em; font-weight: 600; }
+        .badge-ok { background: #d4edda; color: #155724; }
+        .badge-issues { background: #fff3cd; color: #856404; }
+        .badge-critical { background: #f8d7da; color: #721c24; }
+        .badge-nodata { background: #e2e3e5; color: #383d41; }
+        .summary-table { width: 100%; border-collapse: collapse; margin: 15px 0; }
+        .summary-table th, .summary-table td { padding: 10px 14px; text-align: left; border-bottom: 1px solid #eee; }
+        .summary-table th { background: #f8f9fa; font-weight: 600; color: #495057; }
+        .summary-table tr:hover { background: #f8f9fa; }
+        .status-pass { color: #28a745; }
+        .status-fail { color: #dc3545; }
+        .overview-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)); gap: 15px; margin: 20px 0; }
+        .overview-card { background: white; border-radius: 8px; padding: 20px; text-align: center; box-shadow: 0 2px 4px rgba(0,0,0,0.1); }
+        .overview-card .number { font-size: 2em; font-weight: 700; }
+        .overview-card .label { color: #6c757d; font-size: 0.9em; }
+        .content-block { white-space: pre-wrap; font-family: 'SFMono-Regular', Consolas, 'Liberation Mono', Menlo, monospace; font-size: 0.85em; background: #f8f9fa; padding: 15px; border-radius: 4px; border: 1px solid #e9ecef; overflow-x: auto; margin: 10px 0; }
+        .collapsible { cursor: pointer; user-select: none; }
+        .collapsible::before { content: '\25B6  '; font-size: 0.8em; }
+        .collapsible.active::before { content: '\25BC  '; }
+        .collapsible-content { display: none; }
+        .collapsible-content.show { display: block; }
+        .toc { background: white; border-radius: 8px; padding: 20px; margin: 20px 0; box-shadow: 0 2px 4px rgba(0,0,0,0.1); }
+        .toc ul { list-style: none; padding-left: 0; }
+        .toc li { padding: 5px 0; }
+        .toc a { color: #0366d6; text-decoration: none; }
+        .toc a:hover { text-decoration: underline; }
+        .timestamp { color: #6c757d; font-size: 0.9em; }
+        a { color: #0366d6; }
+    </style>
+</head>
+<body>
+<div class="container">
+    <h1>MicroShift CI Release Manager Report</h1>
+    <p class="timestamp">Generated: YYYY-MM-DD HH:MM:SS UTC</p>
+
+    <!-- Overview cards: one per release with total failed jobs count -->
+    <div class="overview-grid">
+        <!-- One card per release -->
+        <div class="overview-card">
+            <div class="number status-fail">N</div>
+            <div class="label">Release X.YY Failed Jobs</div>
+        </div>
+    </div>
+
+    <!-- Table of Contents -->
+    <div class="toc">
+        <h3>Releases Analyzed</h3>
+        <ul>
+            <li><a href="#release-X.YY">Release X.YY</a></li>
+        </ul>
+    </div>
+
+    <!-- Per-release sections -->
+    <div class="release-section" id="release-X.YY">
+        <div class="release-header">
+            <h2>Release X.YY</h2>
+            <span class="badge badge-issues">N failed jobs</span>
+        </div>
+
+        <!-- Embed the full analysis content from analyze-ci-for-release -->
+        <!-- Convert the text report content into formatted HTML -->
+        <!-- Preserve all details: job names, failure types, patterns, severities, links -->
+        <div class="content-block">
+            ... analysis content ...
+        </div>
+    </div>
+
+    <!-- Repeat for each release -->
+</div>
+
+<script>
+// Collapsible sections
+document.querySelectorAll('.collapsible').forEach(function(el) {
+    el.addEventListener('click', function() {
+        this.classList.toggle('active');
+        var content = this.nextElementSibling;
+        content.classList.toggle('show');
+    });
+});
+</script>
+</body>
+</html>
+```
+
+**Content Guidelines**:
+- Do NOT re-analyze or reinterpret the data from `analyze-ci-for-release` - use its output as-is
+- Convert the plain text analysis reports into HTML-formatted content, preserving all information
+- Ensure all Prow job URLs from the original analysis remain clickable links in the HTML
+- Use appropriate badge colors:
+  - `badge-ok`: 0 failed jobs
+  - `badge-issues`: 1+ failed jobs
+  - `badge-critical`: 5+ failed jobs or CRITICAL severity issues present
+  - `badge-nodata`: analysis failed or no data
+- Make per-job details collapsible to keep the page manageable
+- The overview cards should show the number of failed jobs per release at a glance
+
+### Step 5: Report Completion
+
+**Actions**:
+1. Display the path to the generated HTML file
+2. Provide a brief text summary listing each release and its failed job count
+
+**Example Output**:
+```
+HTML report generated: /tmp/microshift-ci-release-manager-20260315-143022.html
+
+Summary:
+  Release 4.19: 3 failed periodic jobs
+  Release 4.20: 7 failed periodic jobs
+  Release 4.21: 0 failed periodic jobs
+  Release 4.22: 12 failed periodic jobs
+```
+
+## Examples
+
+### Example 1: Analyze Multiple Releases
+```
+/analyze-ci-for-release-manager 4.19,4.20,4.21,4.22
+```
+
+### Example 2: Analyze Two Releases
+```
+/analyze-ci-for-release-manager 4.21,4.22
+```
+
+### Example 3: Single Release (still produces HTML)
+```
+/analyze-ci-for-release-manager 4.22
+```
+
+## Notes
+- Each release analysis uses the `analyze-ci-for-release` skill - this command does NOT duplicate that logic
+- The HTML report is self-contained (no external CSS/JS dependencies)
+- All intermediate files from `analyze-ci-for-release` remain available in `/tmp`
+- Releases are analyzed sequentially since each invocation is resource-intensive
+- The HTML file can be opened in any browser for convenient examination
+- If a release analysis fails, it is noted in the report but does not block other releases