ocp-migration-analyst

Automate OpenShift migration analysis to generate a JUSTINRCC-style report.

7|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/rloisell/rl-agents-n-skills --skill ocp-migration-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocp-migration-analyst
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/ocp-migration-analyst
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill ocp-migration-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates comprehensive OpenShift migration analysis across namespace discovery, repository inspection, and gap analysis against target platform requirements, enabling informed planning and reporting for platform migrations.

Core Features & Use Cases

  • End-to-end migration analysis, from namespace discovery through to a concrete migration report (Markdown + PDF).
  • Support for input: OCP namespace prefix, source cluster, GitHub repo, and target platform; outputs a JUSTINRCC-style migration analysis.
  • Automates task planning and report generation to accelerate migration readiness assessments.

Quick Start

Analyze an OpenShift project by supplying namespace, source cluster, repo, and target platform to generate a migration report.

Frequently Asked Questions about ocp-migration-analyst

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

FAQPage Schema
How do I automate OpenShift namespace migration analysis across clusters?

OpenShift migration analysis is automated end-to-end by supplying a namespace prefix, source cluster, GitHub repo, and target platform to generate a JUSTINRCC-style gap analysis and migration plan report.

What is included in an OpenShift migration analysis report?

An OpenShift migration analysis report includes namespace discovery, repository inspection, gap analysis against target platform requirements, network mapping, and a concrete migration plan outputted in both Markdown and PDF formats.

Do I need oc and gh CLIs to generate an OpenShift migration report?

Yes, generating an OpenShift migration report requires the oc and gh CLIs for cluster and repository inspection, along with pandoc and a headless Chrome environment to render the final PDF output.

Can I perform OpenShift migration readiness assessments for a specific GitHub repository?

Yes, OpenShift migration readiness assessments support GitHub repository inspection by taking the repo as an input alongside the source cluster and namespace to evaluate gaps against target platform requirements.

What's the best way to plan an OpenShift platform migration from a source cluster?

The best way to plan an OpenShift platform migration is to use an automated workflow that discovers namespaces, inspects repositories, maps networks, and generates a structured migration plan report in Markdown and PDF.

Are there limitations when using automated migration analysis for OpenShift namespaces?

Limitations of automated OpenShift migration analysis include the strict dependency on oc and gh CLIs, pandoc, and a headless Chrome environment, which are all required to successfully render and output the final PDF report.