What problem does it solve? Manually opening JIRA in a browser to check an issue's status, assignee, comments, or attachments interrupts development workflows. This Skill retrieves complete JIRA issue details directly from the terminal using read-only API calls, keeping credentials in a local .env file that never leaves your machine. ## Core Features & Use Cases - Read-Only Issue Retrieval: Fetches summary, type, status, priority, reporter, assignee, components, labels, fix versions, environment, description, attachments, and comments for any issue key like JIRA-1234. - Secure Credential Handling: Reads JIRA_BASE_URL, JIRA_USER, and JIRA_PASSWORD from a skill-local .env file, validates the HTTPS URL, and never prints or transmits credentials elsewhere. - Flexible Output: Provides formatted human-readable output by default, a --json flag for the raw API response, and a --comments 0 option to omit comments. - Use Case: A developer triaging a bug report asks for JIRA-1234 and immediately receives its status, assignee, description, and full comment thread without leaving the agent session. ## Quick Start Ask the agent to query and summarize JIRA-1234 after copying .env.example to .env and filling in your JIRA credentials.