openshift-developer

Plugin openshift-developer from marketplace ai-helpers in openshift-eng/ai-helpers. Commands read from the repo's manifest — today.

Skills (16)

• address-ci-failures

  Triage and fix PR CI failures caused by the PR's own changes, and rebase the PR when it needs one. Use when has-review-work detects new failing checks or a needs-rebase label, 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 testing guide from a Jira issue, GitHub PR URLs, or both. Use when the user wants test steps, a 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 work (failing checks or a needs-rebase label) 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

• 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-plan

  Use when asked to plan Jira work or when a planning job is assigned. Given a Jira issue and a subtask for planning the implementation of that issue, investigate the specifications and the repository before delivering a planning document to satisfy the subtask, without implementing the work.

• jira-refine

  Refine an OpenShift Jira bug into an evidence-backed disposition — CLOSE, SOLVE, NEEDS_INFO, or NEED_HUMAN_ANALYSIS — with a ticket draft, implementation plan, and backport targets when justified. Use when a bug needs refinement or triage, individually or as the decision primitive of an automated wo

• 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.

• pr-risk-assessment

  Assess an OpenShift pull request's risk tier (Low, Moderate, or Critical) from what its diff changes at runtime and the blast radius of a defect, with an auditable reason. Use when a pull request needs a risk tier for risk-based review, when a reviewer wants a second opinion on how risky a change is

• preassessment

  Read-only assessment of Jira and repository context to decide whether work is ready for implementation or needs planning, decomposition, or clarification. Use when evaluating Jira-driven work before creating an implementation plan or starting implementation.

• 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.

Hooks (1)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/ensure-precommit.sh

Similar plugins