terraform-rhcs-rosa-hcp-issue-triager

To triage ROSA HCP issues, provide a GitHub issue URL to determine ownership, validity, or required remediation. The skill checks official ROSA docs, the provider repository, and module code history to return a strict verdict with cited evidence and a concise fix plan.

Determining ROSA HCP issue ownership involves checking the module codebase, PR history, and the terraform-provider-rhcs repository. The skill analyzes these sources to route the issue correctly, keeping it in the module or escalating it to the provider with supporting evidence.

Generating a fix plan for a valid ROSA HCP module bug requires analyzing the issue against the module codebase and published docs. The skill returns a compact plan including specific risks and step-by-step actions to remediate the identified module bug.

Checking for missing or unsupported ROSA HCP documentation is possible by searching official ROSA docs and published module docs. The skill identifies documentation gaps and returns a verdict citing evidence links to support the conclusion.

Triaging ROSA HCP issues requires checking the terraform-provider-rhcs repository to identify provider capability gaps. The skill uses this repository access to distinguish between module bugs and provider limitations, returning a strict verdict with cited evidence.

Automated issue triage for terraform-rhcs-rosa-hcp accelerates decision-making by searching official docs, provider repositories, and module history simultaneously. It provides evidence-based verdicts and routing decisions, reducing manual investigation effort for maintainers and contributors.