메뉴
Use when needing to know which Red Hat team owns a Konflux-related repository (konflux-ci, hermetoproject, conforma orgs), which JIRA project or component to file issues against, or how the Red Hat Konflux engineering organization maps to the codebase.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when needing to understand Konflux architecture, design decisions, service responsibilities, APIs, build/test/release workflows, or how Konflux components fit together.
Use when updating a Maven project to source its dependencies from a trusted Maven repository instead of Maven Central.
Use to trigger component builds, releases or get a component or application status
Use when tracing Konflux builds from image references, finding build logs from artifacts, or verifying source commits for container images - extracts provenance attestations to navigate from images back to builds and source code
Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.
Use when Konflux pipelines fail, are stuck, timeout, or show errors like ImagePullBackOff. Covers PipelineRun failures, TaskRun issues (Pending, Failed, stuck Running), build errors, and systematic debugging of Tekton pipeline problems using kubectl and logs.
| name | red-hat-konflux-teams |
| description | Use when needing to know which Red Hat team owns a Konflux-related repository (konflux-ci, hermetoproject, conforma orgs), which JIRA project or component to file issues against, or how the Red Hat Konflux engineering organization maps to the codebase. |
Maps repositories across Konflux-related GitHub orgs (konflux-ci, hermetoproject, conforma) to the Red Hat engineering teams that own them and their JIRA metadata.
"Which team owns repo X?" or "Where do I file a bug for X?"
Read references/teams-by-repo.md and find the repo. The table shows the owning team(s), their JIRA project key(s), and a clarification of each team's stake.
"What repos does team Y own?" or "What does team Y work on?"
Read references/repos-by-team.md and find the team section. It lists the team's JIRA project, JIRA components, description, and all owned repos.
"What repos have no owner?"
Read references/unassociated-repos.md for repos not yet mapped to any team.
Teams use two kinds of JIRA locations:
konflux-ci repo owner, repository ownership, JIRA project, JIRA component, file a bug, which team, who owns, team mapping, Red Hat Konflux teams, STONEBLD, KFLUXINFRA, STONEINTG, RELEASE, SRVKP, KONFLUX, KFLUXUI, KFLUXVNGD, KFLUXSE, KFLUXDP, CWFHEALTH, EC, ISV, KAR, PVO11Y, CLOUDDST, SPRE, KFLUXSPRT, ROK, RHELBLD, RELDEV
