feat: Migrate Jira skills to Atlassian Cloud (redhat.atlassian.net)

[EmilienM]

Pull Request Description

Summary

Red Hat Jira has moved from issues.redhat.com to redhat.atlassian.net.
Update jira-activity and jira-upload-chat-log skills to use the new URL
and require JIRA_EMAIL env var for Atlassian Cloud basic auth.

Type of Contribution

• 📝 New command
• 🎯 New skill
• 🤖 New agent
• 💎 New Gemini Gem
• 📚 Documentation update
• 🐛 Bug fix
• 🔄 Refactoring/cleanup
• 🏗️ Infrastructure/tooling
• 📋 New category addition

Summary by CodeRabbit

• Documentation
  • Updated Jira integration setup documentation for jira-activity and jira-upload-chat-log skills
  • Jira host URL updated to redhat.atlassian.net
  • JIRA_EMAIL environment variable now required alongside JIRA_API_TOKEN
  • Refreshed configuration instructions and authentication requirements

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR migrates Jira integration across two skills from the hosted instance (issues.redhat.com) to Atlassian Cloud (redhat.atlassian.net) and changes the authentication method from token-only to basic auth using email and token. Documentation files are updated to reflect the new prerequisites and host URL. The authentication logic in both scripts is refactored: environment variable validation is added for JIRA_EMAIL, client instantiation switches from token_auth to basic_auth=(email, token), and the get_jira_token() function is renamed to get_jira_credentials() with updated return type.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Security considerations

• Credential handling in basic_auth: Verify that basic_auth=(email, token) tuple is not logged or exposed in error messages. basic_auth credentials in the JIRA client must not leak into stack traces or debug output.
• Environment variable validation: Both scripts add early exits when JIRA_EMAIL is missing, but confirm error messages do not expose token values in the exit path.
• No CWE/CVE escalation: The migration from token_auth to basic_auth is functionally equivalent in terms of credential exposure surface area; both require environment variables. Ensure credentials remain in memory only and are not persisted to logs or temporary files.

Action items

• Verify all call sites of get_jira_credentials() in helpers/skills/jira-upload-chat-log/scripts/upload_chat_log.py correctly unpack the tuple return type; check for any remaining references to the old get_jira_token() signature.
• Confirm error handling in both scripts exits cleanly when JIRA_EMAIL or JIRA_API_TOKEN are unset; verify no partial initialization of JIRA client occurs.
• Validate that both scripts test the new authentication path with actual Atlassian Cloud credentials before merging.

🚥 Pre-merge checks | ✅ 2 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	Description covers summary and type of contribution but omits critical sections: Changes Made, Testing and Validation, and Categorization details.	Complete the description by adding detailed Changes Made section, Testing and Validation checks, and Categorization confirmation to match template requirements.
Agentskills.Io Specification Compliance	⚠️ Warning	SKILL.md files missing required YAML frontmatter fields (title, category, license) and lack dedicated Description section per agentskills.io specification.	Add title, category, license to YAML frontmatter and create Description section with current descriptive content for both jira-activity and jira-upload-chat-log files.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title clearly summarizes the primary change: migrating Jira skills to Atlassian Cloud with the new URL.
Ethical Compliance	✅ Passed	No violations of ETHICS.md found. Changes are technical Jira infrastructure updates with no instructions to impersonate any person or replicate persona.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}