User Story

As a HyperShift contributor, I want an automated way to process Renovate dependency PRs so that I can quickly ensure they meet repository contribution standards without manual analysis and Jira ticket creation.

Acceptance Criteria

• [ ] Slash command /process-renovate-pr is available in .claude/commands/
• [ ] Command accepts PR number or "open" to process all open dependency PRs
• [ ] Command supports configurable Jira project and component parameters
• [ ] Command automatically determines target OpenShift version from release branches
• [ ] Command analyzes dependencies (direct vs indirect, usage, impact)
• [ ] Command creates comprehensive Jira tickets with testing instructions
• [ ] Command sets Target Version field in Jira automatically
• [ ] Command updates PR title with Jira reference
• [ ] Command adds detailed explanation comment to PR
• [ ] Command excludes pipeline configuration PRs from processing
• [ ] Command provides progress updates when processing multiple PRs

Implementation Details

Command: /process-renovate-pr [PR_NUMBER|open] [JIRA_PROJECT] [COMPONENT]

Parameters:

• $1 (required): PR number OR "open" to process all open dependency PRs
• $2 (optional): Jira project key (default: "CNTRLPLANE")
• $3 (optional): Jira component name (default: "HyperShift")

Workflow:
1. Determine target OpenShift version from release branches
2. Analyze dependency type, usage, and upstream changes
3. Check for existing Jira tickets to avoid duplicates
4. Create comprehensive Jira ticket with testing instructions
5. Set Target Version field
6. Update PR title and add detailed comment

Features:

• Batch processing support for all open PRs
• Repository-agnostic (detects repo name from git remotes)
• Smart filtering (excludes pipeline config PRs)
• Context-aware testing instructions based on dependency type

Testing

Proof of concept validated with:

• PR #7051: Direct dependency (OpenStack) → CNTRLPLANE-1680
• PR #7049: Indirect dependency (tooling) → CNTRLPLANE-1681

Benefits

• Reduces processing time from ~15 minutes to ~2 minutes per PR
• Ensures consistent, high-quality Jira documentation
• Improves traceability between PRs and tickets
• Enables efficient batch processing of multiple dependency updates