HyperShift team-specific Jira requirements for component selection and conventions
Inherits all available tools
Additional assets for this skill
This skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides HyperShift team-specific conventions for creating Jira issues in CNTRLPLANE and OCPBUGS projects.
This skill is automatically invoked when:
This skill works in conjunction with the cntrlplane skill, adding HyperShift-specific requirements on top of generic CNTRLPLANE/OCPBUGS conventions.
ALL HyperShift issues in CNTRLPLANE and OCPBUGS must have a component set to one of:
Auto-detection based on summary/description keywords:
| Keywords | Component | Confidence |
|---|---|---|
| ARO, Azure, "ARO HCP" | HyperShift / ARO | High |
| ROSA, AWS, "ROSA HCP" | HyperShift / ROSA | High |
| Both ARO and ROSA mentioned | HyperShift | High (multi-platform) |
| "All platforms", "platform-agnostic" | HyperShift | Medium (verify with user) |
| No platform keywords | Prompt user | N/A (cannot auto-detect) |
Important: If no platform keywords are found, do NOT assume platform-agnostic. Prompt the user to clarify which component.
Examples:
Summary: "Enable autoscaling for ROSA HCP clusters"
→ Component: HyperShift / ROSA (auto-detected)
Summary: "ARO HCP control plane pods crash on upgrade"
→ Component: HyperShift / ARO (auto-detected)
Summary: "Multi-cloud support for ARO and ROSA HCP"
→ Component: HyperShift (auto-detected, mentions both platforms)
Summary: "Improve control plane pod scheduling"
→ Component: Prompt user (no keywords, cannot determine platform)
If component cannot be confidently auto-detected:
Prompt example:
Which HyperShift platform does this issue affect?
1. HyperShift / ARO - for ARO HCP (Azure) issues
2. HyperShift / ROSA - for ROSA HCP (AWS) issues
3. HyperShift - for platform-agnostic issues or affects both
Select (1-3):
HyperShift team uses specific version defaults:
Target Version (customfield_12319940):
openshift-4.214.20, 4.22, 4.23)Affects Version/s:
4.21Target Version (customfield_12319940):
4.21In addition to ai-generated-jira (from CNTRLPLANE skill), HyperShift issues may include:
Platform-specific:
aro-hcp - ARO HCP specificrosa-hcp - ROSA HCP specificFeature area:
autoscalingnetworkingobservabilityupgradelifecyclePriority/type:
technical-debtsecurityperformancemcp__atlassian__jira_create_issue(
project_key="CNTRLPLANE",
summary="<issue summary>",
issue_type="Story" | "Task" | "Epic" | "Feature",
description="<formatted description>",
components="HyperShift / ARO" | "HyperShift / ROSA" | "HyperShift",
additional_fields={
"customfield_12319940": "openshift-4.21", # target version
"labels": ["ai-generated-jira"],
"security": {"name": "Red Hat Employee"}
}
)
mcp__atlassian__jira_create_issue(
project_key="OCPBUGS",
summary="<bug summary>",
issue_type="Bug",
description="<formatted bug template>",
components="HyperShift / ARO" | "HyperShift / ROSA" | "HyperShift",
additional_fields={
"versions": [{"name": "4.21"}], # affects version
"customfield_12319940": "4.21", # target version
"labels": ["ai-generated-jira"],
"security": {"name": "Red Hat Employee"}
}
)
Input:
/jira:create story CNTRLPLANE "Enable automatic node pool scaling for ROSA HCP"
Auto-detected:
Interactive prompts:
Result:
Input:
/jira:create bug "ARO HCP control plane pods crash on upgrade"
Auto-detected:
Interactive prompts:
Result:
Input:
/jira:create epic CNTRLPLANE "Improve HyperShift operator observability"
Auto-detected:
Interactive prompts:
Result:
Input:
/jira:create feature CNTRLPLANE "Advanced observability for ROSA and ARO HCP"
Auto-detected:
Interactive prompts:
Result:
Input:
/jira:create story CNTRLPLANE "Improve control plane pod scheduling"
Detection: Summary doesn't contain platform-specific keywords
Prompt:
Which HyperShift platform does this issue affect?
1. HyperShift / ARO - for ARO HCP (Azure) issues
2. HyperShift / ROSA - for ROSA HCP (AWS) issues
3. HyperShift - for platform-agnostic issues or affects both
Select (1-3):
User selects: 3
Result:
User can override auto-detection using --component flag:
# Override auto-detection
/jira:create story CNTRLPLANE "Enable autoscaling for ROSA HCP" --component "HyperShift"
This will use "HyperShift" component instead of auto-detected "HyperShift / ROSA".
Scenario: User specifies component that's not a valid HyperShift component.
Action:
Component "Networking" is not a valid HyperShift component.
HyperShift issues must use one of:
- HyperShift / ARO
- HyperShift / ROSA
- HyperShift
Which component would you like to use?
Scenario: Component cannot be auto-detected and user didn't specify.
Action:
HyperShift issues require a component. Which component?
1. HyperShift / ARO - for ARO HCP (Azure) issues
2. HyperShift / ROSA - for ROSA HCP (AWS) issues
3. HyperShift - for platform-agnostic issues
Select (1-3):
When creating a HyperShift issue:
--component flag provided → Use specified component (validate it's HyperShift)Include platform keywords in summary - Makes auto-detection more accurate
Be specific about platform when known
Use platform-agnostic component wisely
Component consistency within epic
/jira:create - Main command that invokes this skillcntrlplane skill - Generic CNTRLPLANE/OCPBUGS conventions