| name | jira-conventions |
| description | Project and team-specific Jira conventions for CNTRLPLANE, OCPBUGS, GCP, HyperShift, and hosted control plane issues |
Jira Conventions Router
This skill routes to the correct project or team conventions based on the Jira project key, component, or keywords in the issue summary.
Routing Table
Match on project key, component, or summary keywords. Load the corresponding reference file.
By Project Key
By Team / Keywords
Detect these keywords in the issue summary, description, or component to layer team-specific conventions on top of project conventions:
| Keywords | Team Conventions | Reference |
|---|
| HyperShift, ARO HCP, ROSA HCP, hosted control plane | HyperShift team — component selection (HyperShift / ARO, HyperShift / ROSA, HyperShift) | HyperShift conventions |
| GCP HCP, Hypershift on GKE, GKE hosted control plane | GCP HCP team — GCP project conventions, team templates, sizing guide | GCP HCP conventions |
Layering Rules
- Project conventions are loaded first based on the project key
- Team conventions are layered on top when keywords match
- Both can apply simultaneously (e.g., CNTRLPLANE + HyperShift)
- If no project or team matches, skip this skill — the issue uses only type-specific guidance from the
create skill
How to Use
After identifying the matching conventions:
- Read the linked reference file(s)
- Apply project-specific custom fields, version handling, and component requirements
- Layer team-specific conventions if keywords match (component selection, labels, templates)
- Defer to the
create skill for issue-type guidance (story template, bug template, etc.)