openshift-developer¶
Bundle of curated plugins, skills, and MCP servers useful to any OpenShift engineer
Plugin details
- Version: 1.1.30
- Category: Bundle
- Author: github.com/openshift-eng
- Source: Browse repository
- Keywords: openshift bundle meta-plugin
Install¶
/plugin install openshift-developer@ai-helpers
Skills¶
| Skill | Description |
|---|---|
| address-ci-failures | Triage and fix PR CI failures caused by the PR's own changes. Use when has-review-work detects new failing checks, when a PR has CI regressions to investigate, or when deciding whether to fix vs report a CI failure. |
| address-review-pr | Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push. Use when the user wants to address, respond to, or work through PR review feedback. |
| address-review-precommit | Compatibility alias for applying pre-commit review findings through the implement skill. Use when an existing caller has not migrated to openshift-developer:implement. |
| backport | Use when someone asks to backport or cherry-pick a PR to release branches of an openshift/ repository. Drives the full OpenShift backport flow — Jira clone chain, one cherry-pick PR per branch, chain progression — using the deterministic ocp_backport_ tools. |
| check-gates | Repeatedly validate and fix a Jira implementation until tests, lint, builds, requirements, production readiness, and repository cleanliness all pass. Use when a Jira implementation needs its final quality gate before delivery. |
| cherry-pick | Use when the coordinator dispatches a BACKPORT BRIEF for a single branch. Cherry-picks the named commits onto an OpenShift release branch, resolves conflicts conservatively, runs the repository's checks, and pushes the branch to the bot's fork. Never opens a PR. |
| create-pr | Push a completed clean feature branch and create a pull request for a Jira issue. Use when implementation and required quality gates have succeeded and the branch is ready for delivery. |
| generate-test-plan | Generate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both. Use when the user wants test steps, a QE test plan, or a testing guide for code changes. |
| has-review-work | Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent. Use when gating a review-responder loop, polling a PR for actionable feedback, or checking if address-review-pr or address-ci-failures should run. Optional Prow jobs are not CI work. |
| implement | Implement a scoped Jira requirement or apply local pre-commit review findings. Use when a solve workflow needs initial coding or follow-up implementation after code review. |
| jira-solve | Orchestrate the appropriate implementation, review, validation, and PR-building skills for a Jira issue. Use when the user wants an end-to-end fix or feature workflow whose rigor should match ticket complexity. |
| qa-verify-console | Capture before/after screenshots of OpenShift Console PRs running against a live cluster using Puppeteer, generate visual diff comparisons, and post evidence to the PR. Use when a Console PR needs visual QA verification or screenshot-based regression testing. |