edge-tooling

Surface your daily task list — QA-ready tickets, sprint backlog, carry-over items, open PRs, RHEL verification queue, and quarterly reminders. Use at the start of your day to see what needs attention.

Show detailed info about a specific TODO task — its tracked links, notes, and live Jira/PR status. Use when the user asks about a task, wants context to resume work on it, or asks what's needed to finish a ticket. Not for listing all tasks (read the TODO file directly or use edge-ic:sprint-status for sprint-wide views)

End-of-week automation - review active work and prepare next week's TODO

Run the full Prow CI release testing workflow — create PR, trigger jobs, check status, merge PR, download and upload artifacts

Generate interactive PCP performance dashboard from a Prow job URL

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

Download Prow job artifacts, identify root cause of failure, and produce a structured error report

Validate Konflux bootc advisory promotion for QE sign-off — verify advisory YAML, catalog presence, shipment MR, and commit provenance

Always-on commit structuring. Activates whenever the user asks to commit uncommitted changes — plans small, logical commits by default. The user chooses whether to create the commits or just see the proposals. Not for PR creation.

Create JIRA bugs from CI failure reports with cross-release deduplication (dry-run by default)

Analyze CI for multiple MicroShift releases and produce an HTML summary

Attempt to fix CI bugs by opening PRs in openshift/microshift (dry-run by default)

Analyze release health data and produce assessment

Use when analyzing the health of an OCP release cycle — evaluates Features, Initiatives, Epics, and Tasks from Jira to assess progress, identify risks, surface refinement gaps, and recommend actions to keep the team on track toward branch cut

Analyze LVMS health — troubleshoot LVMCluster, volume groups, PVCs, and storage issues on live clusters or must-gather data

Edge OCP Payload Monitor — monitor OpenShift nightly payloads for edge topology (SNO/TNA/TNF) failures with AI-enriched analysis

Analyze a PR for SNO (Single Node OpenShift) security threats with STRIDE/DFD analysis, MITRE ATT&CK and OWASP mapping

Analyze a PR for LVMS (LVM Storage) security threats with STRIDE/DFD analysis, MITRE ATT&CK and OWASP mapping

Analyze a PR for TNA (Two-Node Arbiter) security threats with STRIDE/DFD analysis, MITRE ATT&CK and OWASP mapping

Analyze a PR for TNF (Two-Node Fencing) security threats with STRIDE/DFD analysis, MITRE ATT&CK and OWASP mapping

Analyze CI for LVMS periodic jobs and produce an HTML summary

Download CI Doctor artifacts from a completed prow job and set up a local workdir for continued analysis

Close stale, unlinked, unassigned AI-generated bugs that no longer match current CI failures (dry-run by default)

Regenerate the CI Doctor HTML report from existing data

Check OCP release schedule, verify availability, evaluate z-stream need, or check nightly build gaps

Diagnose TNF cluster issues (shutdown/recovery, etcd, fencing, network, operators), validate proposed procedures, and recommend correct actions based on bare metal test findings

Generate daily standup report from TODO file in Slack-ready format

Update Jira issues based on today's TODO accomplishments

Autonomous PR lifecycle agent — monitors CI, triages review comments, auto-fixes trivial issues, and loops until the PR is ready

Validate MicroShift built artifacts (RPMs and bootc images) produced by ART for a release

Verify a RHEL resource-agents bug fix on a TNF cluster — fetch Jira context, check cluster, patch nodes, run test, generate JIRA report

Triage CodeRabbit review comments on a PR — vet, apply valid fixes, reply

Lint SKILL.md files for quality, correctness, and adherence to the skill guidelines. Use when reviewing, creating, or modifying skills.

Release candidate testing for OCP edge topologies (TNF, TNA, SNO). Launch Prow CI jobs, monitor status, investigate failures, and report results to Jira.

Skeptical second pass on PR review findings — use after /review-pr to filter noise and validate real issues

Create a new MicroShift Enhancement Proposal

Investigate MicroShift runtime problems from SOS report

Analyze MicroShift journal logs to extract statistics about start procedure

Check if a MicroShift CVE Jira ticket is fixed in the latest Brew nightly golang build

Generate test cases for a Jira OCPSTRAT ticket and automate them using Robot Framework